Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-50542media: si470x: Fix use-after-free in si470x_int_in_callback()

Description

In the Linux kernel, the following vulnerability has been resolved: media: si470x: Fix use-after-free in si470x_int_in_callback() syzbot reported use-after-free in si470x_int_in_callback() [1]. This indicates that urb->context, which contains struct si470x_device object, is freed when si470x_int_in_callback() is called. The cause of this issue is that si470x_int_in_callback() is called for freed urb. si470x_usb_driver_probe() calls si470x_start_usb(), which then calls usb_submit_urb() and si470x_start(). If si470x_start_usb() fails, si470x_usb_driver_probe() doesn't kill urb, but it just frees struct si470x_device object, as depicted below: si470x_usb_driver_probe() ... si470x_start_usb() ... usb_submit_urb() retval = si470x_start() return retval if (retval < 0) free struct si470x_device object, but don't kill urb This patch fixes this issue by killing urb when si470x_start_usb() fails and urb is submitted. If si470x_start_usb() fails and urb is not submitted, i.e. submitting usb fails, it just frees struct si470x_device object.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-50542, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 779471110c6f0f7f7c223fc696170ec750ac3531 – < 146bd005ebb01ae190c22af050cb98623958c373
    • affected 779471110c6f0f7f7c223fc696170ec750ac3531 – < 8c6151b8e8dd2d98ad2cd725d26d1e103d989891
    • affected 779471110c6f0f7f7c223fc696170ec750ac3531 – < 52f54fe78cca24850a30865037250f63eb3d5bf7
    • affected 779471110c6f0f7f7c223fc696170ec750ac3531 – < 0ca298d548461d29615f9a2b1309e8dcf4a352c6
    • affected 779471110c6f0f7f7c223fc696170ec750ac3531 – < 1c6447d0fc68650e51586dde79b5090d9d77f13a
    • affected 779471110c6f0f7f7c223fc696170ec750ac3531 – < 6c8aee0c8fcc6dda94315f7908e8fa9bc75abe75
    • affected 779471110c6f0f7f7c223fc696170ec750ac3531 – < 63648a7bd1a7599bcc2040a6d1792363ae4c2e1b
    • affected 779471110c6f0f7f7c223fc696170ec750ac3531 – < 92b0888398e4ba51d93b618a6506781f4e3879c9
    • affected 779471110c6f0f7f7c223fc696170ec750ac3531 – < 7d21e0b1b41b21d628bf2afce777727bd4479aa5
  • Linux · Linux

    • affected 3.6
    • unaffected < 3.6
    • unaffected 4.9.337 – ≤ 4.9.*
    • unaffected 4.14.303 – ≤ 4.14.*
    • unaffected 4.19.270 – ≤ 4.19.*
    • unaffected 5.4.229 – ≤ 5.4.*
    • unaffected 5.10.163 – ≤ 5.10.*
    • unaffected 5.15.86 – ≤ 5.15.*
    • unaffected 6.0.16 – ≤ 6.0.*
    • unaffected 6.1.2 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .