CVE-2026-53207: mm/memory-failure: fix hugetlb_lock AA deadlock in get_huge_page_for_hwpoison
Noroxi assessment
Priority: Monitor (action score 22/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.09% (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 3c2d42b8ee345b17a4ba56b0f6492d1ff4c1178e, 5.16, 77b73b54801ae7137479c141fd0473a491c1dc48; azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 6.6.143.1-1.
Low priority for now. Upgrade to Linux Linux 3c2d42b8ee345b17a4ba56b0f6492d1ff4c1178e, 5.16, 77b73b54801ae7137479c141fd0473a491c1dc48; azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 6.6.143.1-1 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: mm/memory-failure: fix hugetlb_lock AA deadlock in get_huge_page_for_hwpoison Two concurrent madvise(MADV_HWPOISON) calls on the same hugetlb page can trigger a recursive spinlock self-deadlock (AA deadlock) on hugetlb_lock when racing with a concurrent unmap: thread#0 thread#1 -------- -------- madvise(folio, MADV_HWPOISON) -> poisons the folio successfully madvise(folio, MADV_HWPOISON) unmap(folio) try_memory_failure_hugetlb get_huge_page_for_hwpoison spin_lock_irq(&hugetlb_lock) <- held __get_huge_page_for_hwpoison hugetlb_update_hwpoison() -> MF_HUGETLB_FOLIO_PRE_POISONED goto out: folio_put() refcount: 1 -> 0 free_huge_folio() spin_lock_irqsave(&hugetlb_lock) -> AA DEADLOCK! The out: path in __get_huge_page_for_hwpoison() calls folio_put() to drop the GUP reference while the hugetlb_lock is still held by the hugetlb.c wrapper get_huge_page_for_hwpoison(). If concurrent unmap has released the page table mapping reference, folio_put() drops the folio refcount to zero, triggering free_huge_folio() which attempts to re-acquire the non-recursive hugetlb_lock. Fix this by moving hugetlb_lock acquisition from the hugetlb.c wrapper into get_huge_page_for_hwpoison(). Place spin_unlock_irq() before the folio_put() at the out: label so the folio is always released outside the lock. [akpm@linux-foundation.org: fix race, rename label per Miaohe]
- Published
- Jun 25, 2026
- Updated
- Jul 2, 2026
- EPSS
- 0.0% · 0th percentile
- CWE
- CWE-667
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.0%
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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.15.54 and later · before 5.16
- linux linux kernel5.18.1 and later · before 6.1.176
- linux linux kernel6.2 and later · before 6.6.143
- linux linux kernel6.7 and later · before 6.12.94
- linux linux kernel6.13 and later · before 6.18.36
- linux linux kernel6.19 and later · before 7.0.13
- linux linux kernel5.18
- linux linux kernel7.1
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
- 62d1655b922958826b7ec22682c3141746f75064, 5.18affected
- 405ce051236cc65b30bbfe490b28ce60ae6aed85 and later · before fc3ff42cb0cbf947e4600ae9761c3783760050e2affected · git
- 405ce051236cc65b30bbfe490b28ce60ae6aed85 and later · before 77b73b54801ae7137479c141fd0473a491c1dc48affected · git
- 405ce051236cc65b30bbfe490b28ce60ae6aed85 and later · before a33bfed648c10f5a1519981dbfad80841191edc8affected · git
- 405ce051236cc65b30bbfe490b28ce60ae6aed85 and later · before dd77a83915b07e2b0205adb284f08b39ae31dc4baffected · git
- 405ce051236cc65b30bbfe490b28ce60ae6aed85 and later · before bf7ba8f96c258c30393814491930ae4ecdc5fe5eaffected · git
- 405ce051236cc65b30bbfe490b28ce60ae6aed85 and later · before 3c2d42b8ee345b17a4ba56b0f6492d1ff4c1178eaffected · git
- 5.15.54 and later · before 5.16affected · semver
- before 5.18not affected · semver
- 6.1.176 and later · up to and including 6.1.*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.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.13-1 | 7.0.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-53204Jun 25, 2026 · firmware: stratix10-rsu: Fix NULL deref on rsu_send_msg() timeout in probe22Monitor
- ← EarlierCVE-2026-53206Jun 25, 2026 · accel/ivpu: Add bounds check for firmware runtime memory22Monitor
- Later →CVE-2026-53210Jun 25, 2026 · tee: shm: fix shm leak in register_shm_helper()22Monitor
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 | 3c2d42b8ee345b17a4ba56b0f6492d1ff4c1178e | Vendor (CNA) |
| Linux Linux | 5.16 | Vendor (CNA) |
| Linux Linux | 77b73b54801ae7137479c141fd0473a491c1dc48 | Vendor (CNA) |
| Linux Linux | a33bfed648c10f5a1519981dbfad80841191edc8 | Vendor (CNA) |
| Linux Linux | bf7ba8f96c258c30393814491930ae4ecdc5fe5e | Vendor (CNA) |
| Linux Linux | dd77a83915b07e2b0205adb284f08b39ae31dc4b | Vendor (CNA) |
| Linux Linux | fc3ff42cb0cbf947e4600ae9761c3783760050e2 | Vendor (CNA) |
| azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 | 6.6.143.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.176-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.
No history yet (it accumulates with the daily EPSS job).
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/77b73b54801ae7137479c141fd0473a491c1dc48
- git.kernel.org/stable/c/a33bfed648c10f5a1519981dbfad80841191edc8
- git.kernel.org/stable/c/bf7ba8f96c258c30393814491930ae4ecdc5fe5e
- git.kernel.org/stable/c/dd77a83915b07e2b0205adb284f08b39ae31dc4b
- git.kernel.org/stable/c/fc3ff42cb0cbf947e4600ae9761c3783760050e2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.