Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-49751

w1: fix WARNING after calling w1_process()

Medium5.5EPSS 0.19%
Published
Updated
Reserved
Assigned by
Linux

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.

Scores

CVSS scores of CVE-2022-49751, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (5 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

  • CWE-noinfo Not enough information

Affected products

  • Linux · Linux

    • affected 3c52e4e627896b42152cc6ff98216c302932227e – < 190b5c3bbd5df685bb1063bda048831d72b8f1d4
    • affected 3c52e4e627896b42152cc6ff98216c302932227e – < bccd6df4c177b1ad766f16565ccc298653d027d0
    • affected 3c52e4e627896b42152cc6ff98216c302932227e – < 276052159ba94d4d9f5b453fb4707d6798c6b845
    • affected 3c52e4e627896b42152cc6ff98216c302932227e – < 216f35db6ec6a667cd9db4838d657c1d2f4684da
    • affected 3c52e4e627896b42152cc6ff98216c302932227e – < 89c62cee5d4d65ac75d99b5f986f7f94290e888f
    • affected 3c52e4e627896b42152cc6ff98216c302932227e – < cfc7462ff824ed6718ed0272ee9aae88e20d469a
    • affected 3c52e4e627896b42152cc6ff98216c302932227e – < 36225a7c72e9e3e1ce4001b6ce72849f5c9a2d3b
  • Linux · Linux

    • affected 2.6.28
    • unaffected < 2.6.28
    • unaffected 4.14.305 – ≤ 4.14.*
    • unaffected 4.19.272 – ≤ 4.19.*
    • unaffected 5.4.231 – ≤ 5.4.*
    • unaffected 5.10.166 – ≤ 5.10.*
    • unaffected 5.15.91 – ≤ 5.15.*
    • unaffected 6.1.9 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References (7)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49751 badge
[![CVE-2022-49751](https://trackcve.app/badge/CVE-2022-49751.svg)](https://trackcve.app/cve/CVE-2022-49751)

Record last updated .