{"api_version":"1","generated_at":"2026-05-28T00:40:46+00:00","cve":"CVE-2026-46041","urls":{"html":"https://cve.report/CVE-2026-46041","api":"https://cve.report/api/cve/CVE-2026-46041.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-46041","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-46041"},"summary":{"title":"greybus: gb-beagleplay: fix sleep in atomic context in hdlc_tx_frames()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ngreybus: gb-beagleplay: fix sleep in atomic context in hdlc_tx_frames()\n\nhdlc_append() calls usleep_range() to wait for circular buffer space,\nbut it is called with tx_producer_lock (a spinlock) held via\nhdlc_tx_frames() -> hdlc_append_tx_frame()/hdlc_append_tx_u8()/etc.\nSleeping while holding a spinlock is illegal and can trigger\n\"BUG: scheduling while atomic\".\n\nFix this by moving the buffer-space wait out of hdlc_append() and into\nhdlc_tx_frames(), before the spinlock is acquired.  The new flow:\n\n 1. Pre-calculate the worst-case encoded frame length.\n 2. Wait (with sleep) outside the lock until enough space is available,\n    kicking the TX consumer work to drain the buffer.\n 3. Acquire the spinlock, re-verify space, and write the entire frame\n    atomically.\n\nThis ensures that sleeping only happens without any lock held, and\nthat frames are either fully enqueued or not written at all.\n\nThis bug is found by CodeQL static analysis tool (interprocedural\nsleep-in-atomic query) and my code review.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-05-27 14:17:23","updated_at":"2026-05-27 14:48:03"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/51667fe2d9294d66e0228b9f51d1f01b6680a641","name":"https://git.kernel.org/stable/c/51667fe2d9294d66e0228b9f51d1f01b6680a641","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9f2b87bcdfed55145acbf932dc12f2c057145cad","name":"https://git.kernel.org/stable/c/9f2b87bcdfed55145acbf932dc12f2c057145cad","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b2801647c203a38e013802e9e9616b5bfac64968","name":"https://git.kernel.org/stable/c/b2801647c203a38e013802e9e9616b5bfac64968","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/6b526dca0966f2370835765019a54319b78fca8d","name":"https://git.kernel.org/stable/c/6b526dca0966f2370835765019a54319b78fca8d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-46041","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46041","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ec558bbfea671ac020a6dc6be8bf8f0ee556cce0 9f2b87bcdfed55145acbf932dc12f2c057145cad git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ec558bbfea671ac020a6dc6be8bf8f0ee556cce0 b2801647c203a38e013802e9e9616b5bfac64968 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ec558bbfea671ac020a6dc6be8bf8f0ee556cce0 51667fe2d9294d66e0228b9f51d1f01b6680a641 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected ec558bbfea671ac020a6dc6be8bf8f0ee556cce0 6b526dca0966f2370835765019a54319b78fca8d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.7","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.7 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.86 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.27 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.4 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/greybus/gb-beagleplay.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"9f2b87bcdfed55145acbf932dc12f2c057145cad","status":"affected","version":"ec558bbfea671ac020a6dc6be8bf8f0ee556cce0","versionType":"git"},{"lessThan":"b2801647c203a38e013802e9e9616b5bfac64968","status":"affected","version":"ec558bbfea671ac020a6dc6be8bf8f0ee556cce0","versionType":"git"},{"lessThan":"51667fe2d9294d66e0228b9f51d1f01b6680a641","status":"affected","version":"ec558bbfea671ac020a6dc6be8bf8f0ee556cce0","versionType":"git"},{"lessThan":"6b526dca0966f2370835765019a54319b78fca8d","status":"affected","version":"ec558bbfea671ac020a6dc6be8bf8f0ee556cce0","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/greybus/gb-beagleplay.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.7"},{"lessThan":"6.7","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.86","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.27","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.86","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.27","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.4","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1-rc1","versionStartIncluding":"6.7","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ngreybus: gb-beagleplay: fix sleep in atomic context in hdlc_tx_frames()\n\nhdlc_append() calls usleep_range() to wait for circular buffer space,\nbut it is called with tx_producer_lock (a spinlock) held via\nhdlc_tx_frames() -> hdlc_append_tx_frame()/hdlc_append_tx_u8()/etc.\nSleeping while holding a spinlock is illegal and can trigger\n\"BUG: scheduling while atomic\".\n\nFix this by moving the buffer-space wait out of hdlc_append() and into\nhdlc_tx_frames(), before the spinlock is acquired.  The new flow:\n\n 1. Pre-calculate the worst-case encoded frame length.\n 2. Wait (with sleep) outside the lock until enough space is available,\n    kicking the TX consumer work to drain the buffer.\n 3. Acquire the spinlock, re-verify space, and write the entire frame\n    atomically.\n\nThis ensures that sleeping only happens without any lock held, and\nthat frames are either fully enqueued or not written at all.\n\nThis bug is found by CodeQL static analysis tool (interprocedural\nsleep-in-atomic query) and my code review."}],"providerMetadata":{"dateUpdated":"2026-05-27T12:56:54.418Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/9f2b87bcdfed55145acbf932dc12f2c057145cad"},{"url":"https://git.kernel.org/stable/c/b2801647c203a38e013802e9e9616b5bfac64968"},{"url":"https://git.kernel.org/stable/c/51667fe2d9294d66e0228b9f51d1f01b6680a641"},{"url":"https://git.kernel.org/stable/c/6b526dca0966f2370835765019a54319b78fca8d"}],"title":"greybus: gb-beagleplay: fix sleep in atomic context in hdlc_tx_frames()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-46041","datePublished":"2026-05-27T12:56:54.418Z","dateReserved":"2026-05-13T15:03:33.094Z","dateUpdated":"2026-05-27T12:56:54.418Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-05-27 14:17:23","lastModifiedDate":"2026-05-27 14:48:03","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"46041","Ordinal":"1","Title":"greybus: gb-beagleplay: fix sleep in atomic context in hdlc_tx_f","CVE":"CVE-2026-46041","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"46041","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ngreybus: gb-beagleplay: fix sleep in atomic context in hdlc_tx_frames()\n\nhdlc_append() calls usleep_range() to wait for circular buffer space,\nbut it is called with tx_producer_lock (a spinlock) held via\nhdlc_tx_frames() -> hdlc_append_tx_frame()/hdlc_append_tx_u8()/etc.\nSleeping while holding a spinlock is illegal and can trigger\n\"BUG: scheduling while atomic\".\n\nFix this by moving the buffer-space wait out of hdlc_append() and into\nhdlc_tx_frames(), before the spinlock is acquired.  The new flow:\n\n 1. Pre-calculate the worst-case encoded frame length.\n 2. Wait (with sleep) outside the lock until enough space is available,\n    kicking the TX consumer work to drain the buffer.\n 3. Acquire the spinlock, re-verify space, and write the entire frame\n    atomically.\n\nThis ensures that sleeping only happens without any lock held, and\nthat frames are either fully enqueued or not written at all.\n\nThis bug is found by CodeQL static analysis tool (interprocedural\nsleep-in-atomic query) and my code review.","Type":"Description","Title":"greybus: gb-beagleplay: fix sleep in atomic context in hdlc_tx_f"}]}}}