PT-2026-43908 · Linux · Linux
Published
2026-05-27
·
Updated
2026-05-27
·
CVE-2026-46041
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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:
- Pre-calculate the worst-case encoded frame length.
- Wait (with sleep) outside the lock until enough space is available, kicking the TX consumer work to drain the buffer.
- 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.
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux