CVE-2025-40319: bpf: Sync pending IRQ work before freeing ring buffer
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.14% (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 10ca3b2eec384628bc9f5d8190aed9427ad2dde6, 430e15544f11f8de26b2b5109c7152f71b78295e, 47626748a2a00068dbbd5836d19076637b4e235b.
Low priority for now. Upgrade to Linux Linux 10ca3b2eec384628bc9f5d8190aed9427ad2dde6, 430e15544f11f8de26b2b5109c7152f71b78295e, 47626748a2a00068dbbd5836d19076637b4e235b 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: Sync pending IRQ work before freeing ring buffer Fix a race where irq_work can be queued in bpf_ringbuf_commit() but the ring buffer is freed before the work executes. In the syzbot reproducer, a BPF program attached to sched_switch triggers bpf_ringbuf_commit(), queuing an irq_work. If the ring buffer is freed before this work executes, the irq_work thread may accesses freed memory. Calling `irq_work_sync(&rb->work)` ensures that all pending irq_work complete before freeing the buffer.
- Published
- Dec 8, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- —
Report tools
Action score
31
Monitor
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.
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
- 5.8affected
- 457f44363a8894135c85b7a9afd2bd8196db24ab and later · before 47626748a2a00068dbbd5836d19076637b4e235baffected · git
- 457f44363a8894135c85b7a9afd2bd8196db24ab and later · before de2ce6b14bc3e565708a39bdba3ef9162aeffc72affected · git
- 457f44363a8894135c85b7a9afd2bd8196db24ab and later · before e1828c7a8d8135e21ff6adaaa9458c32aae13b11affected · git
- 457f44363a8894135c85b7a9afd2bd8196db24ab and later · before 6451141103547f4efd774e912418a3b4318046c6affected · git
- 457f44363a8894135c85b7a9afd2bd8196db24ab and later · before 10ca3b2eec384628bc9f5d8190aed9427ad2dde6affected · git
- 457f44363a8894135c85b7a9afd2bd8196db24ab and later · before 430e15544f11f8de26b2b5109c7152f71b78295eaffected · git
- 457f44363a8894135c85b7a9afd2bd8196db24ab and later · before 4e9077638301816a7d73fa1e1b4c1db4a7e3b59caffected · git
- before 5.8not affected · semver
- 5.10.247 and later · up to and including 5.10.*not 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 | before 6.1.159-1 | 6.1.159-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.8-1 | 6.17.8-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-2025-40317Dec 8, 2025 · regmap: slimbus: fix bus_context pointer in regmap init calls31Monitor
- ← EarlierCVE-2025-40318Dec 8, 2025 · Bluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once35Monitor
- Later →CVE-2025-40320Dec 8, 2025 · smb: client: fix potential cfid UAF in smb2_query_info_compound39Monitor
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 | 10ca3b2eec384628bc9f5d8190aed9427ad2dde6 | Vendor (CNA) |
| Linux Linux | 430e15544f11f8de26b2b5109c7152f71b78295e | Vendor (CNA) |
| Linux Linux | 47626748a2a00068dbbd5836d19076637b4e235b | Vendor (CNA) |
| Linux Linux | 4e9077638301816a7d73fa1e1b4c1db4a7e3b59c | Vendor (CNA) |
| Linux Linux | 6451141103547f4efd774e912418a3b4318046c6 | Vendor (CNA) |
| Linux Linux | de2ce6b14bc3e565708a39bdba3ef9162aeffc72 | Vendor (CNA) |
| Linux Linux | e1828c7a8d8135e21ff6adaaa9458c32aae13b11 | Vendor (CNA) |
| debian:linux | 6.1.159-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).
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
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
- 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/430e15544f11f8de26b2b5109c7152f71b78295e
- git.kernel.org/stable/c/47626748a2a00068dbbd5836d19076637b4e235b
- git.kernel.org/stable/c/4e9077638301816a7d73fa1e1b4c1db4a7e3b59c
- git.kernel.org/stable/c/6451141103547f4efd774e912418a3b4318046c6
- git.kernel.org/stable/c/de2ce6b14bc3e565708a39bdba3ef9162aeffc72
- git.kernel.org/stable/c/e1828c7a8d8135e21ff6adaaa9458c32aae13b11
Vendor advisories and official records. Exploit/PoC links are deliberately left out.