CVE-2026-53324

net: mana: Use pci_name() for debugfs directory naming

MEDIUM
5.5
CVSS Score
Published: June 26, 2026 at 07:41 PM UTC
Updated: July 6, 2026 at 08:23 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.13 ≤ v < 6.18.336.13 ≤ v < 7.0.106.13 ≤ v < 7.16.19 ≤ v < 7.0.106.136607c17c6c5e029da03a90085db22daf518232bf
Vendor states this is fixed in 34dbd7b819544c99c9d96b400fe4db613f40ac4b (fixed)
Vendor states this is fixed in 9211eb97e8f8c28bf9313ab97862d143dbbbef97 (fixed)
Vendor states this is fixed in c116f07ab9d22bb6f355f3cf9e44c1e6a47fe559 (fixed)
Vendor states this is fixed in 6.13 (unaffected)
Vendor states this is fixed in 6.18.33 (unaffected)
Vendor states this is fixed in 7.0.10 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card