PatchSiren cyber security CVE debrief
CVE-2026-23374 Linux CVE debrief
A Linux kernel vulnerability allows for a bug in the blktrace subsystem, which can lead to a BUG when using __this_cpu_read() in preemptible code. This issue arises from tracing_record_cmdline() being called in process context with preemption enabled, contrary to its design for scheduler context with preemption disabled. The bug was discovered in blktests/blktrace/002, causing a BUG with __this_cpu_read() in preemptible code. The issue is due to tracing_record_cmdline() being called in process context. Linux kernel developers, maintainers, and users of Linux systems, especially those utilizing blktrace for monitoring block device activity, should assess their exposure to this and
- Vendor
- Linux
- Product
- Unknown
- CVSS
- MEDIUM 5.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-03-25
- Original CVE updated
- 2026-10-15
- Advisory published
- 2026-03-25
- Advisory updated
- 2026-10-15
Who should care
Linux kernel developers, maintainers, and users of Linux systems, especially those utilizing blktrace for monitoring block device activity, should assess their exposure to this vulnerability and prioritize verification and patching of affected systems.
Why it matters
CVE-2026-23374 is a Linux kernel vulnerability in the blktrace subsystem that can cause a BUG in preemptible code. Linux kernel developers and users should assess exposure, verify affected systems, and apply patches to prevent potential system instability.
- Verification of affected Linux kernel versions and system exposure is necessary.
- Potential for system crashes or instability if the blktrace subsystem is used in vulnerable configurations.
- Monitoring system logs for suspicious blktrace activity may be required to detect potential exploitation attempts.
- Patching affected systems should be prioritized to prevent potential issues.
Technical summary
The Linux kernel vulnerability CVE-2026-23374 arises from improper use of __this_cpu_read() and __this_cpu_write() in preemptible context within the blktrace subsystem. This can lead to a BUG when tracing_record_cmdline() is called in process context with preemption enabled. The issue was discovered in blktests/blktrace/002. Linux kernel developers and users should assess exposure, verify affected systems, and apply patches to prevent potential system instability. The vulnerability highlights the importance of thorough verification and patching of affected systems to prevent potential issues.
Defensive priority
Linux kernel maintainers and users should assess exposure and prioritize verification of affected systems, especially those utilizing blktrace for block device tracing.
Recommended defensive actions
- Review and apply patches provided by Linux kernel maintainers for CVE-2026-23374.
- Assess system exposure and verify if running affected Linux kernel versions.
- Monitor system logs for blktrace-related errors indicative of potential exploitation attempts.
- Perform thorough verification of system exposure, especially for Linux kernel versions and configurations utilizing blktrace.
- Implement compensating controls for exposed systems while remediation is scheduled and verified.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
- Review relevant monitoring, detection, and logs for exposed assets that need extra review.
Evidence notes
The bug was found in blktests/blktrace/002, causing a BUG with __this_cpu_read() in preemptible code. The issue is due to tracing_record_cmdline() being called in process context with preemption enabled, contrary to its design. This highlights the need for thorough verification of system exposure and prompt patching of affected systems. Evidence is limited to the supplied source corpus and kernel developer reports. Defensive verification tasks include reviewing system logs for blktrace-related errors and assessing the potential for
Sources and references
Verified primary and authoritative sources
-
CVE-2026-23374 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-23374
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-23374 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-23374
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/59efa088752b1c380a0475974679850cc8aef907
416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/6e5c3ddf17a2cb1722301bbbd15655fcc20ed1ce
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/aaba6ee63ba65b026401c94e2dd16b9f6e895934
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/da46b5dfef48658d03347cda21532bcdbb521e67
416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/e5584932ac1dacc182c430d09e2b5490d1d4372b
416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.