CVE-2026-46041: 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…

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.

Affected

6 ranges

Vendor	Product	Version range	Fixed in
linux	linux	—	—
linux	linux	>= ec558bbfea671ac020a6dc6be8bf8f0ee556cce0 < 9f2b87bcdfed55145acbf932dc12f2c057145cad	9f2b87bcdfed55145acbf932dc12f2c057145cad
linux	linux	>= ec558bbfea671ac020a6dc6be8bf8f0ee556cce0 < b2801647c203a38e013802e9e9616b5bfac64968	b2801647c203a38e013802e9e9616b5bfac64968
linux	linux	>= ec558bbfea671ac020a6dc6be8bf8f0ee556cce0 < 51667fe2d9294d66e0228b9f51d1f01b6680a641	51667fe2d9294d66e0228b9f51d1f01b6680a641
linux	linux	>= ec558bbfea671ac020a6dc6be8bf8f0ee556cce0 < 6b526dca0966f2370835765019a54319b78fca8d	6b526dca0966f2370835765019a54319b78fca8d
linux	linux_kernel	—	—