In the Linux kernel, the following vulnerability has been resolved: net: mana: Use pci_name() for debugfs directory naming Use pci_name(pdev) for… (CVE-2026-53324)
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.
AI Analysis
Technical Summary
The Linux kernel mana network driver previously used pci_slot_name(pdev->slot) for naming per-device debugfs directories for virtual functions (VFs) and a hardcoded "0" for physical functions (PFs). This approach caused two issues: dereferencing a NULL pointer for pdev->slot in certain environments (e.g., VFIO passthrough or nested KVM), and naming collisions in debugfs directories leading to -EEXIST errors. The fix replaces these with pci_name(pdev), which returns a unique and always valid BDF address, preventing NULL pointer dereferences and naming conflicts.
Potential Impact
This vulnerability can cause a denial of service by crashing the kernel or preventing debugfs directory creation due to NULL pointer dereference and directory naming collisions. There is no impact on confidentiality or integrity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: net: mana: Use pci_name() for debugfs directory naming Use pci_name(pdev) for… (CVE-2026-53324)
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.
CVSS v3.1
Score 5.5medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel mana network driver previously used pci_slot_name(pdev->slot) for naming per-device debugfs directories for virtual functions (VFs) and a hardcoded "0" for physical functions (PFs). This approach caused two issues: dereferencing a NULL pointer for pdev->slot in certain environments (e.g., VFIO passthrough or nested KVM), and naming collisions in debugfs directories leading to -EEXIST errors. The fix replaces these with pci_name(pdev), which returns a unique and always valid BDF address, preventing NULL pointer dereferences and naming conflicts.
Potential Impact
This vulnerability can cause a denial of service by crashing the kernel or preventing debugfs directory creation due to NULL pointer dereference and directory naming collisions. There is no impact on confidentiality or integrity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-78w3-3c52-99hr
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53324"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a4c33fd27e9c797195f2820
Added to database: 07/06/2026, 23:02:21 UTC
Last enriched: 07/06/2026, 23:09:22 UTC
Last updated: 07/31/2026, 19:24:49 UTC
Views: 19
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.