CVE-2026-74363: bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs
Noroxi assessment
Priority: Monitor (action score 31/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.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0497ff765746d9b2d17445c8f7cc737b36c0152a, 5.15.212, 53649846e0437d1d9b7cb993cfe54c367addf7ae.
Low priority for now. Upgrade to Linux Linux 0497ff765746d9b2d17445c8f7cc737b36c0152a, 5.15.212, 53649846e0437d1d9b7cb993cfe54c367addf7ae 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: bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs commit 4f375ade6aa9 ("bpf: Avoid RCU context warning when unpinning htab with internal structs") moved inode cleanup from ->free_inode() into ->destroy_inode() to avoid sleeping in RCU context when calling bpf_any_put(). However this removed the RCU delay on freeing the inode itself and the cached symlink body (i_link), both of which can be accessed by RCU pathwalk (pick_link, may_lookup etc.). This causes a use-after-free when a concurrent unlinkat() drops the last inode reference and destroy_inode() frees the inode immediately, while another task is still walking the path in RCU mode and reads inode->i_opflags (offset +2) inside current_time() -> is_mgtime(). KASAN reports: BUG: KASAN: slab-use-after-free in is_mgtime include/linux/fs.h:2313 Read of size 2 at addr ffff8880407e4282 (offset +2 = i_opflags) The rules (per Al Viro): ->destroy_inode() called immediately, can sleep, use for blocking cleanup e.g. bpf_any_put() ->free_inode() called after RCU grace period, use for freeing inode and anything RCU-accessible e.g. i_link Fix: split the two concerns properly: - keep bpf_any_put() in bpf_destroy_inode() since it is blocking and needs to run promptly - introduce bpf_free_inode() to handle kfree(i_link) and free_inode_nonrcu() with proper RCU delay, preventing the UAF
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Is your version affected? Check itNoroxi 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
- de2d2baecc84cc7fca52eec2b9b55d89c93e3565, 6.18affected
- e28616ca3d67e745ecb2f10eba4a626e1fc9a203 and later · before ea1c243c39e32b7fc1c2edfe32081ff7e30a877caffected · git
- 743a620c661994c7f0938e6dd32fb0883fb1e0ea and later · before 5fecb71c10c28aef276ba49c718dc961745fdcf0affected · git
- b6e9645be9eb93f7aff3ca887f8edb6f1d63358f and later · before c70d0f9114c3cc156f6029a400c4eb7e6f7c82b2affected · git
- ee04cff9ed4d6bb25802f5cecfcd0750500410f3 and later · before 53649846e0437d1d9b7cb993cfe54c367addf7aeaffected · git
- 4f375ade6aa9f37fd72d7a78682f639772089eed and later · before 61f19729728243c82476dee31315143ed3275e7faffected · git
- 4f375ade6aa9f37fd72d7a78682f639772089eed and later · before 0497ff765746d9b2d17445c8f7cc737b36c0152aaffected · git
- 4f375ade6aa9f37fd72d7a78682f639772089eed and later · before b93c55b4932dd7e32dca8cf34a3443cc87a02906affected · git
- 5.15.195 and later · before 5.15.212affected · semver
- 6.1.157 and later · before 6.1.178affected · 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 | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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-74359Aug 15, 2026 · configfs_lookup(): don't leave ->s_dentry dangling on failure31Monitor
- ← EarlierCVE-2026-74361Aug 15, 2026 · nvme: fix FDP fdpcidx bounds check39Monitor
- Later →CVE-2026-74365Aug 15, 2026 · nvdimm/btt: Handle preemption in BTT lane acquisition29Monitor
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 | 0497ff765746d9b2d17445c8f7cc737b36c0152a | Vendor (CNA) |
| Linux Linux | 5.15.212 | Vendor (CNA) |
| Linux Linux | 53649846e0437d1d9b7cb993cfe54c367addf7ae | Vendor (CNA) |
| Linux Linux | 5fecb71c10c28aef276ba49c718dc961745fdcf0 | Vendor (CNA) |
| Linux Linux | 6.1.178 | Vendor (CNA) |
| Linux Linux | 6.12.97 | Vendor (CNA) |
| Linux Linux | 6.18 | Vendor (CNA) |
| Linux Linux | 6.6.145 | Vendor (CNA) |
| Linux Linux | 61f19729728243c82476dee31315143ed3275e7f | Vendor (CNA) |
| Linux Linux | b93c55b4932dd7e32dca8cf34a3443cc87a02906 | Vendor (CNA) |
| Linux Linux | c70d0f9114c3cc156f6029a400c4eb7e6f7c82b2 | Vendor (CNA) |
| Linux Linux | ea1c243c39e32b7fc1c2edfe32081ff7e30a877c | Vendor (CNA) |
| debian:linux | 6.1.180-1 · 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.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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 (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/53649846e0437d1d9b7cb993cfe54c367addf7ae
- git.kernel.org/stable/c/5fecb71c10c28aef276ba49c718dc961745fdcf0
- git.kernel.org/stable/c/61f19729728243c82476dee31315143ed3275e7f
- git.kernel.org/stable/c/b93c55b4932dd7e32dca8cf34a3443cc87a02906
- git.kernel.org/stable/c/c70d0f9114c3cc156f6029a400c4eb7e6f7c82b2
- git.kernel.org/stable/c/ea1c243c39e32b7fc1c2edfe32081ff7e30a877c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.