CVE-2026-46267: nfc: hci: shdlc: Stop timers and work before freeing context

Published Jun 3, 2026
·
Updated

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

nfc: hci: shdlc: Stop timers and work before freeing context

llcshdlcdeinit() purges SHDLC skb queues and frees the llcshdlc structure while its timers and state machine work may still be active.

Timer callbacks can schedule smwork, and smwork accesses SHDLC state and the skb queues. If teardown happens in parallel with a queued/running work item, it can lead to UAF and other shutdown races.

Stop all SHDLC timers and cancel smwork synchronously before purging the queues and freeing the context.

Found by Linux Verification Center (linuxtesting.org) with SVACE.

Affected Software

7 affected components
The Linux Foundation Linux Kernel
Linux Linux kernel>=3.7<5.15.202
Linux Linux kernel>=5.16<6.1.165
Linux Linux kernel>=6.2<6.6.128
Linux Linux kernel>=6.7<6.12.75
Linux Linux kernel>=6.13<6.18.14
Linux Linux kernel>=6.19<6.19.4

Event History

Jun 3, 2026
CVE Published
via MITRE·03:50 PM
Data Sourced
via MITRE·03:50 PM
Description
Data Sourced
via NVD·06:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-46267?

CVE-2026-46267 is rated with a risk severity of 40.

2

How do I fix CVE-2026-46267?

To fix CVE-2026-46267, update the Linux kernel to the latest version where this vulnerability has been addressed.

3

What components are affected by CVE-2026-46267?

CVE-2026-46267 affects the NFC subsystem in the Linux kernel, specifically related to SHDLC context management.

4

Can CVE-2026-46267 lead to system instability?

Yes, CVE-2026-46267 can lead to system instability due to improper handling of timers and state machines.

5

Is CVE-2026-46267 publicly disclosed?

Yes, CVE-2026-46267 was publicly disclosed on June 3, 2026.

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