Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-40319bpf: Sync pending IRQ work before freeing ring buffer

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 8 months later

    Published

  3. · 10 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-40319, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Deferred3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.15% · top 95% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 457f44363a8894135c85b7a9afd2bd8196db24ab – < 47626748a2a00068dbbd5836d19076637b4e235b
    • affected 457f44363a8894135c85b7a9afd2bd8196db24ab – < de2ce6b14bc3e565708a39bdba3ef9162aeffc72
    • affected 457f44363a8894135c85b7a9afd2bd8196db24ab – < e1828c7a8d8135e21ff6adaaa9458c32aae13b11
    • affected 457f44363a8894135c85b7a9afd2bd8196db24ab – < 6451141103547f4efd774e912418a3b4318046c6
    • affected 457f44363a8894135c85b7a9afd2bd8196db24ab – < 10ca3b2eec384628bc9f5d8190aed9427ad2dde6
    • affected 457f44363a8894135c85b7a9afd2bd8196db24ab – < 430e15544f11f8de26b2b5109c7152f71b78295e
    • affected 457f44363a8894135c85b7a9afd2bd8196db24ab – < 4e9077638301816a7d73fa1e1b4c1db4a7e3b59c
  • Linux · Linux

    • affected 5.8
    • unaffected < 5.8
    • unaffected 5.10.247 – ≤ 5.10.*
    • unaffected 5.15.197 – ≤ 5.15.*
    • unaffected 6.1.159 – ≤ 6.1.*
    • unaffected 6.6.117 – ≤ 6.6.*
    • unaffected 6.12.58 – ≤ 6.12.*
    • unaffected 6.17.8 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-40319 badge
[![CVE-2025-40319](https://cveledger.app/badge/CVE-2025-40319.svg)](https://cveledger.app/cve/CVE-2025-40319)

Record last updated .