CVE-2025-39749

Source
https://cve.org/CVERecord?id=CVE-2025-39749
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-39749.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2025-39749
Downstream
Related
Published
2025-09-11T16:52:21.228Z
Modified
2026-03-20T12:43:02.135952Z
Summary
rcu: Protect ->defer_qs_iw_pending from data race
Details

In the Linux kernel, the following vulnerability has been resolved:

rcu: Protect ->deferqsiw_pending from data race

On kernels built with CONFIGIRQWORK=y, when rcureadunlock() is invoked within an interrupts-disabled region of code [1], it will invoke rcureadunlock_special(), which uses an irq-work handler to force the system to notice when the RCU read-side critical section actually ends. That end won't happen until interrupts are enabled at the soonest.

In some kernels, such as those booted with rcutree.use_softirq=y, the irq-work handler is used unconditionally.

The per-CPU rcudata structure's ->deferqsiwpending field is updated by the irq-work handler and is both read and updated by rcureadunlock_special(). This resulted in the following KCSAN splat:


BUG: KCSAN: data-race in rcupreemptdeferredqshandler / rcureadunlock_special

read to 0xffff96b95f42d8d8 of 1 bytes by task 90 on cpu 8: rcureadunlock_special+0x175/0x260 __rcureadunlock+0x92/0xa0 rtspinunlock+0x9b/0xc0 __localbhenable+0x10d/0x170 __localbhenableip+0xfb/0x150 rcudobatch+0x595/0xc40 rcucpukthread+0x4e9/0x830 smpbootthreadfn+0x24d/0x3b0 kthread+0x3bd/0x410 retfromfork+0x35/0x40 retfromforkasm+0x1a/0x30

write to 0xffff96b95f42d8d8 of 1 bytes by task 88 on cpu 8: rcupreemptdeferredqshandler+0x1e/0x30 irqworksingle+0xaf/0x160 runirqworkd+0x91/0xc0 smpbootthreadfn+0x24d/0x3b0 kthread+0x3bd/0x410 retfromfork+0x35/0x40 retfromfork_asm+0x1a/0x30

no locks held by irqwork/8/88. irq event stamp: 200272 hardirqs last enabled at (200272): [<ffffffffb0f56121>] finishtask_switch+0x131/0x320 hardirqs last disabled at (200271): [<ffffffffb25c7859>] _schedule+0x129/0xd70 softirqs last enabled at (0): [<ffffffffb0ee093f>] copyprocess+0x4df/0x1cc0 softirqs last disabled at (0): [<0000000000000000>] 0x0


The problem is that irq-work handlers run with interrupts enabled, which means that rcupreemptdeferredqshandler() could be interrupted, and that interrupt handler might contain an RCU read-side critical section, which might invoke rcureadunlockspecial(). In the strict KCSAN mode of operation used by RCU, this constitutes a data race on the ->deferqsiwpending field.

This commit therefore disables interrupts across the portion of the rcupreemptdeferredqshandler() that updates the ->deferqsiw_pending field. This suffices because this handler is not a fast path.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/39xxx/CVE-2025-39749.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
0864f057b050bc6dd68106b3185e02db5140012d
Fixed
74f58f382a7c8333f8d09701aefaa25913bdbe0e
Fixed
f937759c7432d6151b73e1393b6517661813d506
Fixed
0ad84d62217488e679ecc90e8628980dcc003de3
Fixed
b5de8d80b5d049f051b95d9b1ee50ae4ab656124
Fixed
b55947b725f190396f475d5d0c59aa855a4d8895
Fixed
e35e711c78c8a4c43330c0dcb1c4d507a19c20f4
Fixed
90de9c94ea72327cfa9c2c9f6113c23a513af60b
Fixed
55e11f6776798b27cf09a7aa0d718415d4fc9cf5
Fixed
90c09d57caeca94e6f3f87c49e96a91edd40cbfd

Database specific

source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-39749.json"