CVE-2026-46041
Last modified
CVE-2026-46041 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: greybus: gb-beagleplay: fix sleep in atomic context in hdlc_tx_frames() hdlc_append() calls usleep_range() to wait for circular buffer space, but it is called with tx_producer_lock (a spinlock) held via hdlc_tx_frames() -> hdlc_append_tx_frame()/hdlc_append_tx_u8()/etc. Sleeping while holding a spinlock is illegal and can trigger "BUG: scheduling while atomic". Fix this by moving the buffer-space wait out of hdlc_append() and into hdlc_tx_frames(), before the spinlock is acquired. The new flow: 1. EPSS estimates a 0.12% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: greybus: gb-beagleplay: fix sleep in atomic context in hdlc_tx_frames() hdlc_append() calls usleep_range() to wait for circular buffer space, but it is called with tx_producer_lock (a spinlock) held via hdlc_tx_frames() -> hdlc_append_tx_frame()/hdlc_append_tx_u8()/etc. Sleeping while holding a spinlock is illegal and can trigger "BUG: scheduling while atomic". Fix this by moving the buffer-space wait out of hdlc_append() and into hdlc_tx_frames(), before the spinlock is acquired. The new flow: 1. Pre-calculate the worst-case encoded frame length. 2. Wait (with sleep) outside the lock until enough space is available, kicking the TX consumer work to drain the buffer. 3. Acquire the spinlock, re-verify space, and write the entire frame atomically. This ensures that sleeping only happens without any lock held, and that frames are either fully enqueued or not written at all. This bug is found by CodeQL static analysis tool (interprocedural sleep-in-atomic query) and my code review.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.7, < 6.12.86 |
| Linux | Linux Kernel | >= 6.13, < 6.18.27 |
| Linux | Linux Kernel | >= 6.19, < 7.0.4 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-46041?
How severe is CVE-2026-46041?
How do I fix CVE-2026-46041?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-46036In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46037In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-46038In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46039In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-4604The Klubraum Membership Request plugin for WordPress is vuln…5.3
- CVE-2026-46040In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46042In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46043In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-46044In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46045In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46046In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46047In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-46041?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
