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-2026-43357iio: gyro: mpu3050-core: fix pm_runtime error handling

Description

In the Linux kernel, the following vulnerability has been resolved: iio: gyro: mpu3050-core: fix pm_runtime error handling The return value of pm_runtime_get_sync() is not checked, allowing the driver to access hardware that may fail to resume. The device usage count is also unconditionally incremented. Use pm_runtime_resume_and_get() which propagates errors and avoids incrementing the usage count on failure. In preenable, add pm_runtime_put_autosuspend() on set_8khz_samplerate() failure since postdisable does not run when preenable fails.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 3 days 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-2026-43357, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.12% · top 98% of all CVEs (14 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 3904b28efb2c780c23dcddfb87e07fe0230661e5 – < 935f57dd43492240e1ca220dd065d624efece6be
    • affected 3904b28efb2c780c23dcddfb87e07fe0230661e5 – < 8544c488e50206f00630a8bbba43d2c8bd290345
    • affected 3904b28efb2c780c23dcddfb87e07fe0230661e5 – < 35f54e7bcb1eccdc6e5bff06580eeef2e0ff3677
    • affected 3904b28efb2c780c23dcddfb87e07fe0230661e5 – < 2a86a396aa001a9f9ba2d37dda36573a76f17c90
    • affected 3904b28efb2c780c23dcddfb87e07fe0230661e5 – < 66c0d1d600e7be034959cf49edab104cb5a39258
    • affected 3904b28efb2c780c23dcddfb87e07fe0230661e5 – < 42685cf96e28262e0b84d74447f3d99f3f6a72e0
    • affected 3904b28efb2c780c23dcddfb87e07fe0230661e5 – < 7a3dec5b265cf87678b10c98a72a435a8e769bb7
    • affected 3904b28efb2c780c23dcddfb87e07fe0230661e5 – < acc3949aab3e8094641a9c7c2768de1958c88378
  • Linux · Linux

    • affected 4.10
    • unaffected < 4.10
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.78 – ≤ 6.12.*
    • unaffected 6.18.19 – ≤ 6.18.*
    • unaffected 6.19.9 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .