VulnerabilityPublished 26 Jun 2026Updated 6 Nov 2026

CVE-2026-53324: Linux kernel · net: mana: Use pci_name() for debugfs directory naming

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in c116f07ab9d22bb6f355f3cf9e44c1e6a47fe559 : 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

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 c116f07ab9d22bb6f355f3cf9e44c1e6a47fe559, 9211eb97e8f8c28bf9313ab97862d143dbbbef97, 34dbd7b819544c99c9d96b400fe4db613f40ac4b

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to c116f07ab9d22bb6f355f3cf9e44c1e6a47fe559, 9211eb97e8f8c28bf9313ab97862d143dbbbef97 or 34dbd7b819544c99c9d96b400fe4db613f40ac4b.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 6607c17c6c5e029da03a90085db22daf518232bf, < c116f07ab9d22bb6f355f3cf9e44c1e6a47fe559	Fixed in c116f07ab9d22bb6f355f3cf9e44c1e6a47fe559
LinuxLinux	Affected ≥ 6607c17c6c5e029da03a90085db22daf518232bf, < 9211eb97e8f8c28bf9313ab97862d143dbbbef97	Fixed in 9211eb97e8f8c28bf9313ab97862d143dbbbef97
LinuxLinux	Affected ≥ 6607c17c6c5e029da03a90085db22daf518232bf, < 34dbd7b819544c99c9d96b400fe4db613f40ac4b	Fixed in 34dbd7b819544c99c9d96b400fe4db613f40ac4b
LinuxLinux	Affected =6.13	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: net: mana: Use pci_name() for debugfs directory naming Use pci_name(pdev) for the per-device debugfs directory instead of hardcoded "0" for PFs and pci_slot_name(pdev->slot) for VFs. The previous approach had two issues: 1. pci_slot_name() dereferences pdev->slot, which can be NULL for VFs in environments like generic VFIO passthrough or nested KVM, causing a NULL pointer dereference. 2. Multiple PFs would all use "0", and VFs across different PCI domains or buses could share the same slot name, leading to -EEXIST errors from debugfs_create_dir(). pci_name(pdev) returns the unique BDF address, is always valid, and is unique across the system.

References

Community reviews

Loading reviews…