Skip to main content
VulnerabilityPublished Updated

CVE-2026-53327: Linux kernel · debugobjects: Do not fill_pool() if pi_blocked_on

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in a3383df76f0d7a597066df018409eb9e5e698064 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:49 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in a3383df76f0d7a597066df018409eb9e5e698064, 33bee10644f8fff3b1a0187ad5ad34513e5e8e72, 8a680d54f1adf3e3aa815578684556716fda6f0c +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 4bedcc28469a24fe481a8a31b3584e6070457ddb, < a3383df76f0d7a597066df018409eb9e5e698064
Fixed in
  • a3383df76f0d7a597066df018409eb9e5e698064
LinuxLinuxAffected
  • ≥ 4bedcc28469a24fe481a8a31b3584e6070457ddb, < 33bee10644f8fff3b1a0187ad5ad34513e5e8e72
Fixed in
  • 33bee10644f8fff3b1a0187ad5ad34513e5e8e72
LinuxLinuxAffected
  • ≥ 4bedcc28469a24fe481a8a31b3584e6070457ddb, < 8a680d54f1adf3e3aa815578684556716fda6f0c
Fixed in
  • 8a680d54f1adf3e3aa815578684556716fda6f0c
LinuxLinuxAffected
  • ≥ 4bedcc28469a24fe481a8a31b3584e6070457ddb, < 5f41161059fd0f1bbf18c90f3180e38cc45a14eb
Fixed in
  • 5f41161059fd0f1bbf18c90f3180e38cc45a14eb
LinuxLinuxAffected
  • ≥ 4bedcc28469a24fe481a8a31b3584e6070457ddb, < 3f6a3b24ab7b9d51f6f4778254bef0e5847beb55
Fixed in
  • 3f6a3b24ab7b9d51f6f4778254bef0e5847beb55
LinuxLinuxAffected
  • ≥ 4bedcc28469a24fe481a8a31b3584e6070457ddb, < 3a408cae608d9c075dd3a9e5cfc03b3cb0726863
Fixed in
  • 3a408cae608d9c075dd3a9e5cfc03b3cb0726863

Description

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.

References

Community reviews

Loading reviews…