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-2026-90247bpf: Fix mmap_lock leak in irq_work path

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix mmap_lock leak in irq_work path stack_map_get_build_id_offset() introduced a per-CPU irq_work to defer mmap_read_unlock() from NMI context, and bpf_find_vma() later reused the same mmap_unlock_work. Both callers only check whether the work is busy before taking mmap_lock, so a nested caller can reuse the slot before the first caller queues it. Two read locks may then be acquired while only one deferred unlock runs, leaking a read lock and blocking exit_mmap(). Reserve the per-CPU slot before mmap_read_trylock(). Use the same wrapper in stackmap and bpf_find_vma() so both callers release the reservation on trylock failure. Keep rejecting the slot while the irq_work remains busy. Release it after the irq_work callback unlocks the mm.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 43 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected eac9153f2b584c702cea02c1f1a57d85aa9aea42 – < d6d091873e12d1de36d7228c4f452e6cace3a23e
    • affected eac9153f2b584c702cea02c1f1a57d85aa9aea42 – < b6c9daf6097f9b39162b8e736a6ac7caf5ef6fc8
    • affected eac9153f2b584c702cea02c1f1a57d85aa9aea42 – < 931f62311c058d79f29548f20943969bb441ce87
    • affected eac9153f2b584c702cea02c1f1a57d85aa9aea42 – < a052ad5edccf5319f50ed955de4368f8318a9f20
    • affected eac9153f2b584c702cea02c1f1a57d85aa9aea42 – < 051f2da26ce377f683b938a3382e0f16d02f3139
    • affected eac9153f2b584c702cea02c1f1a57d85aa9aea42 – < fa9dcacdcdf487f0ffef64bf67622f1caed509f1
    • affected a7f4da875c16f3b8bef0d9ec67528111045bfcd8
    • affected f1838da73cccb238b8be4ef464fce0168dc7ba84
    • affected 4.19.92 – < 4.20
    • affected 5.4.7 – < 5.5
  • Linux · Linux

    • affected 5.5
    • unaffected < 5.5
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .