CVE-2026-46041greybus: gb-beagleplay: fix sleep in atomic context in hdlc_tx_frames()
- 5.5MediumCVSS base score
- 0.14%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 14 days later
· 14 days later
Published
- 18 days later
· 18 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.14% · top 97% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected ec558bbfea671ac020a6dc6be8bf8f0ee556cce0 – < 9f2b87bcdfed55145acbf932dc12f2c057145cad
- affected ec558bbfea671ac020a6dc6be8bf8f0ee556cce0 – < b2801647c203a38e013802e9e9616b5bfac64968
- affected ec558bbfea671ac020a6dc6be8bf8f0ee556cce0 – < 51667fe2d9294d66e0228b9f51d1f01b6680a641
- affected ec558bbfea671ac020a6dc6be8bf8f0ee556cce0 – < 6b526dca0966f2370835765019a54319b78fca8d
- affected 6.7
- unaffected < 6.7
- unaffected 6.12.86 – ≤ 6.12.*
- unaffected 6.18.27 – ≤ 6.18.*
- unaffected 7.0.4 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References4
- https://git.kernel.org/stable/c/9f2b87bcdfed55145acbf932dc12f2c057145cad (opens in a new tab)
- https://git.kernel.org/stable/c/b2801647c203a38e013802e9e9616b5bfac64968 (opens in a new tab)
- https://git.kernel.org/stable/c/51667fe2d9294d66e0228b9f51d1f01b6680a641 (opens in a new tab)
- https://git.kernel.org/stable/c/6b526dca0966f2370835765019a54319b78fca8d (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-32422 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-46041)Record last updated .