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-99132xfs: don't hold buffer locks across sync transaction commit in xfs_sync_sb_buf

Description

In the Linux kernel, the following vulnerability has been resolved: xfs: don't hold buffer locks across sync transaction commit in xfs_sync_sb_buf xfs_sync_sb_buf() holds sb/rtsb buffer locks across a synchronous xfs_trans_commit(), which flushes the CIL push workqueue internally. If shutdown occurs during the CIL push, xfs_buf_item_unpin() needs to lock these buffers to fail them, causing a deadlock: setlabel: holds buf lock -> flush_workqueue(xfs-cil) CIL push worker: xfs_buf_item_unpin -> xfs_buf_lock(same buf) Remove the xfs_trans_bhold() calls so that commit releases the buffer locks normally. After the sync commit, re-acquire the buffers via mp->m_sb_bp / mp->m_rtsb_bp for the on-disk writeback.

Timeline

  1. ID reserved

    By Linux

  2. · 33 days later

    Published

  3. · 2 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.18% · top 93% of all CVEs (17 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 f7664b31975bd893190708e76b2c424328f0c49b – < 16468281da17263095bd1906cf2d16a972f10791
    • affected f7664b31975bd893190708e76b2c424328f0c49b – < 45f124f3902bfae6a366d124db04f707264176fb
    • affected f7664b31975bd893190708e76b2c424328f0c49b – < d900946853c2d183fa0e199bae9ddbcd21795a18
    • affected f7664b31975bd893190708e76b2c424328f0c49b – < 83b2e511cf9ba22904b167e00fcbd85169b50b2c
    • affected f7664b31975bd893190708e76b2c424328f0c49b – < acd7f2f9b822b6e126f3e3c99c173e62aa315b6f
    • affected f7664b31975bd893190708e76b2c424328f0c49b – < e5456dec79c71c8ef8f9f9adb77d320f113b34db
    • affected f7664b31975bd893190708e76b2c424328f0c49b – < 6353e5cd8c43d6e805cacbfbfecf4103571a7ff8
    • affected f7664b31975bd893190708e76b2c424328f0c49b – < 41a28c865d1d5843f8cb9e0af17a8f4d9e2961ff
  • Linux · Linux

    • affected 4.18
    • unaffected < 4.18
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.161 – ≤ 6.6.*
    • unaffected 6.12.115 – ≤ 6.12.*
    • unaffected 6.18.59 – ≤ 6.18.*
    • unaffected 7.2.13 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .