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-80534xfs: fix ilock leak on error in xfs_dq_get_next_id

Description

In the Linux kernel, the following vulnerability has been resolved: xfs: fix ilock leak on error in xfs_dq_get_next_id xfs_dq_get_next_id() takes the quota inode ILOCK before calling xfs_iread_extents(). If xfs_iread_extents() fails, the function returns immediately without releasing the lock, leaking the quota inode ILOCK. This can leave the quota inode locked and cause subsequent quota operations to hang. Fix this by jumping to a common unlock path on error instead of returning directly.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 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

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)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 bda250dbaf39f67f8910e183853e4e6a9e5ce899 – < e4c05ebd01e910bccd4f7e9517c7353982e27763
    • affected bda250dbaf39f67f8910e183853e4e6a9e5ce899 – < 6401b99a285cd4cfb2949ba44675541b91ad7e4f
    • affected bda250dbaf39f67f8910e183853e4e6a9e5ce899 – < 0865e4fca02e418fd2423fae9a887dee87b778a1
    • affected bda250dbaf39f67f8910e183853e4e6a9e5ce899 – < ed8bfb43de71213cfdbbe833b2c2817250e18b1a
    • affected bda250dbaf39f67f8910e183853e4e6a9e5ce899 – < e270d539b8a2e0cb8f617fee47a7b083c0088361
    • affected bda250dbaf39f67f8910e183853e4e6a9e5ce899 – < 514a5d42d4188fc5f1499a8d654c717ebf981193
    • affected bda250dbaf39f67f8910e183853e4e6a9e5ce899 – < 08bed2b67d2ee79d3e138c344d8dcfa4c9b26a38
    • affected bda250dbaf39f67f8910e183853e4e6a9e5ce899 – < 63320a0f70f66f311f4bccff3af0719c2119f46c
  • Linux · Linux

    • affected 4.13
    • unaffected < 4.13
    • unaffected 5.10.267 – ≤ 5.10.*
    • unaffected 5.15.217 – ≤ 5.15.*
    • unaffected 6.1.184 – ≤ 6.1.*
    • unaffected 6.6.153 – ≤ 6.6.*
    • unaffected 6.12.105 – ≤ 6.12.*
    • unaffected 6.18.46 – ≤ 6.18.*
    • unaffected 7.1.10 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .