CVE-2026-98862: audit: fix exe mark UAF in kill_rules()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 0afb9202c1fb88387d0577524bf9785664bdd802, 11715656540360906235d724fde5349631425073, 304960900991157e6883bdf0b39782b690545ee8; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 0afb9202c1fb88387d0577524bf9785664bdd802, 11715656540360906235d724fde5349631425073, 304960900991157e6883bdf0b39782b690545ee8; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: audit: fix exe mark UAF in kill_rules() kill_rules() removes mixed AUDIT_DIR and AUDIT_EXE rules when an audit tree is pruned. It drops entry->rule.exe before removing the rule from the RCU-visible filter lists. After a rule has been installed with AUDIT_ADD_RULE, which requires CAP_AUDIT_CONTROL, removing the watched directory can race with another task that is still evaluating the rule. In that case, fsnotify can free the executable mark before the reader reaches audit_mark_compare(), causing a use-after-free. KASAN reports: BUG: KASAN: slab-use-after-free in audit_mark_compare+0x8d/0xa0 Unlink the published rules from the RCU-visible lists and retain them on tree->rules for cleanup. If any rule has an executable mark, wait for a single RCU grace period before removing the marks and scheduling the entries for freeing. Otherwise, call_rcu() already provides the required deferred freeing without a synchronous wait.
- Published
- Oct 18, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.3affected
- 34d99af52ad40bd498ba66970579a5bc1fb1a3bc and later · before 8d9c97fb262067933ff4452db19e692d26622352affected · git
- 34d99af52ad40bd498ba66970579a5bc1fb1a3bc and later · before 11715656540360906235d724fde5349631425073affected · git
- 34d99af52ad40bd498ba66970579a5bc1fb1a3bc and later · before 0afb9202c1fb88387d0577524bf9785664bdd802affected · git
- 34d99af52ad40bd498ba66970579a5bc1fb1a3bc and later · before 9aee3caeff4dd4126d84f67607b95cec8719b867affected · git
- 34d99af52ad40bd498ba66970579a5bc1fb1a3bc and later · before 304960900991157e6883bdf0b39782b690545ee8affected · git
- 34d99af52ad40bd498ba66970579a5bc1fb1a3bc and later · before 88633025f20ba9c32ccdb3efc86eafdf98cb825caffected · git
- 34d99af52ad40bd498ba66970579a5bc1fb1a3bc and later · before f2cc5462b78559c7628a9f8ac9a9592e7783183aaffected · git
- 34d99af52ad40bd498ba66970579a5bc1fb1a3bc and later · before aa650d87a498844060eecb1d336f4d46f4d1b0b3affected · git
- before 4.3not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.10-1 | 7.2.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98860Oct 18, 2026 · HID: bpf: cast size to ssize_t when checking hid_bpf_hw_request0Monitor
- ← EarlierCVE-2026-98861Oct 18, 2026 · fprobe: Use guard(rcu_sched_notrace) and check rcu_is_watching()0Monitor
- Later →CVE-2026-98863Oct 18, 2026 · KVM: x86: Re-pend GET_NESTED_STATE_PAGES if getting said pages fails0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0afb9202c1fb88387d0577524bf9785664bdd802 | Vendor (CNA) |
| Linux Linux | 11715656540360906235d724fde5349631425073 | Vendor (CNA) |
| Linux Linux | 304960900991157e6883bdf0b39782b690545ee8 | Vendor (CNA) |
| Linux Linux | 88633025f20ba9c32ccdb3efc86eafdf98cb825c | Vendor (CNA) |
| Linux Linux | 8d9c97fb262067933ff4452db19e692d26622352 | Vendor (CNA) |
| Linux Linux | 9aee3caeff4dd4126d84f67607b95cec8719b867 | Vendor (CNA) |
| Linux Linux | aa650d87a498844060eecb1d336f4d46f4d1b0b3 | Vendor (CNA) |
| Linux Linux | f2cc5462b78559c7628a9f8ac9a9592e7783183a | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 6, 2026+18 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/11715656540360906235d724fde5349631425073
- git.kernel.org/stable/c/304960900991157e6883bdf0b39782b690545ee8
- git.kernel.org/stable/c/88633025f20ba9c32ccdb3efc86eafdf98cb825c
- git.kernel.org/stable/c/8d9c97fb262067933ff4452db19e692d26622352
- git.kernel.org/stable/c/9aee3caeff4dd4126d84f67607b95cec8719b867
- git.kernel.org/stable/c/aa650d87a498844060eecb1d336f4d46f4d1b0b3
- git.kernel.org/stable/c/f2cc5462b78559c7628a9f8ac9a9592e7783183a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.