Incorrect audit records for ptrace(2) syscall requests
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in p16, p7, p11 and 1 more.
When auditing a system call executed via ptrace(PT_SC_REMOTE), the kernel passed the return value of an internal setup function to AUDIT_SYSCALL_EXIT() rather than the actual result of the executed system call. As a result, committed audit records for system calls which returned an error do not reflect the true outcome of the operation. That is, they indicate that the operation succeeded when it in fact failed. Audit records for system calls executed via ptrace(PT_SC_REMOTE) may show an incorrect error status. An attacker with the ability to debug a process could use this to produce misleading audit trails, potentially undermining audit-based Intrusion Detection Systems (IDS).
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| FreeBSD | freebsd | =14.3, =14.4, =15.0, =15.1 | |
| FreeBSD | >=14.3-RELEASE <p16, >=14.4-RELEASE <p7, >=15.0-RELEASE <p11, >=15.1-RELEASE <p1 | p16, p7, p11, p1 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket