Answer in brief
CVE-2026-53327 records a Unknown severity vulnerability in debugobjects: Do not fill_pool() if pi_blocked_on. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4bedcc28469a24fe481a8a31b3584e6070457ddb <8a680d54f1adf3e3aa815578684556716fda6f0c || >=4bedcc28469a24fe481a8a31b3584e6070457ddb <a3383df76f0d7a597066df018409eb9e5e698064 || >=4bedcc28469a24fe481a8a31b3584e6070457ddb <3f6a3b24ab7b9d51f6f4778254bef0e5847beb55 || >=4bedcc28469a24fe481a8a31b3584e6070457ddb <3a408cae608d9c075dd3a9e5cfc03b3cb0726863 || >=4bedcc28469a24fe481a8a31b3584e6070457ddb <33bee10644f8fff3b1a0187ad5ad34513e5e8e72 || >=4bedcc28469a24fe481a8a31b3584e6070457ddb <5f41161059fd0f1bbf18c90f3180e38cc45a14eb | 8a680d54f1adf3e3aa815578684556716fda6f0c, a3383df76f0d7a597066df018409eb9e5e698064, 3f6a3b24ab7b9d51f6f4778254bef0e5847beb55, 3a408cae608d9c075dd3a9e5cfc03b3cb0726863, 33bee10644f8fff3b1a0187ad5ad34513e5e8e72, 5f41161059fd0f1bbf18c90f3180e38cc45a14eb |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Jul 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 1, 2026
In the Linux kernel, the following vulnerability has been resolved: debugobjects: Do not fill_pool() if pi_blocked_on On RT enabled kernels, fill_pool() ends up calling rtlock_lock(), which asserts if current::pi_blocked_on is set, because a task can obviously only block on one lock as otherwise the priority inheritenace chain gets corrupted. Prevent this by expanding the conditional to take current::pi_blocked_on into account.
Quoted source text, attributed separately from HOL analysis.