CVE-2026-46009: PCI: endpoint: pci-epf-ntb: Remove duplicate resource teardown

Published May 27, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

PCI: endpoint: pci-epf-ntb: Remove duplicate resource teardown

epfntbepcdestroy() duplicates the teardown that the caller is supposed to do later. This leads to an oops when .allowlink fails or when .droplink is performed. Remove the helper.

Also drop pciepcput(). EPC device refcounting is tied to configfs EPC group lifetime, and pciepcput() in the .droplink path is sufficient.

Affected Software

8 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=5.12<5.15.209
Linux Linux kernel>=5.16<6.1.175
Linux Linux kernel>=6.2<6.6.140
Linux Linux kernel>=6.7<6.12.86
Linux Linux kernel>=6.13<6.18.27
Linux Linux kernel>=6.19<7.0.4
Microsoft azl3 kernel 6.6.139.1-1<6.6.141.1-1
6.6.141.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.141.1-1

Event History

May 27, 2026
CVE Published
via MITRE·12:56 PM
Data Sourced
via MITRE·12:56 PM
Description
Data Sourced
via NVD·02:17 PM
RemedyDescriptionSeverityAffected Software
May 28, 2026
Data Sourced
via Microsoft·08:07 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:07 AM
Affected Software
Updated
via Microsoft·08:07 AM
DescriptionSeverity

Frequently Asked Questions

1

What conditions trigger the kernel crash?

An oops can occur when the PCI endpoint function NTB driver's .allow_link operation fails or when its .drop_link operation is performed. The issue is caused by duplicate resource teardown in the affected path.

2

Which systems are exposed?

Systems using the Linux kernel PCI endpoint NTB function driver are implicated. The provided data also identifies Microsoft azl3 kernel 6.6.139.1-1 as affected software.

3

Is authentication or user interaction required to trigger the issue?

The supplied vector lists no privileges required and no user interaction required. It also indicates network attack vector and low attack complexity, but the provided description does not specify the exact remote interface or request needed to reach the vulnerable driver path.

4

What is the impact of successful exploitation?

The reported impact is high availability impact, with no reported confidentiality or integrity impact. The failure manifests as a kernel oops.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203