CVE-2022-49751

w1: fix WARNING after calling w1_process()

MEDIUM

5.5

CVSS Score

Published: March 27, 2025 at 04:42 PM UTC

Updated: June 17, 2026 at 05:19 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: w1: fix WARNING after calling w1_process() I got the following WARNING message while removing driver(ds2482): ------------[ cut here ]------------ do not call blocking ops when !TASK_RUNNING; state=1 set at [<000000002d50bfb6>] w1_process+0x9e/0x1d0 [wire] WARNING: CPU: 0 PID: 262 at kernel/sched/core.c:9817 __might_sleep+0x98/0xa0 CPU: 0 PID: 262 Comm: w1_bus_master1 Tainted: G N 6.1.0-rc3+ #307 RIP: 0010:__might_sleep+0x98/0xa0 Call Trace: exit_signals+0x6c/0x550 do_exit+0x2b4/0x17e0 kthread_exit+0x52/0x60 kthread+0x16d/0x1e0 ret_from_fork+0x1f/0x30 The state of task is set to TASK_INTERRUPTIBLE in loop in w1_process(), set it to TASK_RUNNING when it breaks out of the loop to avoid the warning.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

2.6.28 ≤ v < 4.14.3052.6.28 ≤ v < 4.19.2722.6.28 ≤ v < 5.10.1662.6.28 ≤ v < 5.15.912.6.28 ≤ v < 5.4.2312.6.28 ≤ v < 6.1.92.6.28 ≤ v < 6.24.15 ≤ v < 4.19.2724.20 ≤ v < 5.4.2315.11 ≤ v < 5.15.915.16 ≤ v < 6.1.95.5 ≤ v < 5.10.1663c52e4e627896b42152cc6ff98216c302932227e6.2 rc1 6.2 rc2 6.2 rc3 6.2 rc4

Vendor states this is fixed in 190b5c3bbd5df685bb1063bda048831d72b8f1d4 (fixed)

Vendor states this is fixed in 216f35db6ec6a667cd9db4838d657c1d2f4684da (fixed)

Vendor states this is fixed in 276052159ba94d4d9f5b453fb4707d6798c6b845 (fixed)

Vendor states this is fixed in 36225a7c72e9e3e1ce4001b6ce72849f5c9a2d3b (fixed)

Vendor states this is fixed in 89c62cee5d4d65ac75d99b5f986f7f94290e888f (fixed)

Vendor states this is fixed in bccd6df4c177b1ad766f16565ccc298653d027d0 (fixed)

Vendor states this is fixed in cfc7462ff824ed6718ed0272ee9aae88e20d469a (fixed)

Vendor states this is fixed in 2.6.28 (unaffected)

Vendor states this is fixed in 4.14.305 (unaffected)

Vendor states this is fixed in 4.19.272 (unaffected)

Vendor states this is fixed in 5.10.166 (unaffected)

Vendor states this is fixed in 5.15.91 (unaffected)

Vendor states this is fixed in 5.4.231 (unaffected)

Vendor states this is fixed in 6.1.9 (unaffected)

Vendor states this is fixed in 6.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references