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-31740counter: rz-mtu3-cnt: do not use struct rz_mtu3_channel's dev member

Description

In the Linux kernel, the following vulnerability has been resolved: counter: rz-mtu3-cnt: do not use struct rz_mtu3_channel's dev member The counter driver can use HW channels 1 and 2, while the PWM driver can use HW channels 0, 1, 2, 3, 4, 6, 7. The dev member is assigned both by the counter driver and the PWM driver for channels 1 and 2, to their own struct device instance, overwriting the previous value. The sub-drivers race to assign their own struct device pointer to the same struct rz_mtu3_channel's dev member. The dev member of struct rz_mtu3_channel is used by the counter sub-driver for runtime PM. Depending on the probe order of the counter and PWM sub-drivers, the dev member may point to the wrong struct device instance, causing the counter sub-driver to do runtime PM actions on the wrong device. To fix this, use the parent pointer of the counter, which is assigned during probe to the correct struct device, not the struct device pointer inside the shared struct rz_mtu3_channel.

Timeline

  1. ID reserved

    By Linux

  2. · 53 days later

    Published

  3. · 10 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-31740, 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 (16 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 0be8907359df4c62319f5cb2c6981ff0d9ebf35a – < 28a371be901ef44ee03726c2575d7d6795521fe0
    • affected 0be8907359df4c62319f5cb2c6981ff0d9ebf35a – < 633dfbf0eb2766c597c1a59dd83035c82e14791d
    • affected 0be8907359df4c62319f5cb2c6981ff0d9ebf35a – < 6562290225c197e2e193a53de2a517815288dcd1
    • affected 0be8907359df4c62319f5cb2c6981ff0d9ebf35a – < 63be324c795262f0e316c6fe9b329d83afa1ec93
    • affected 0be8907359df4c62319f5cb2c6981ff0d9ebf35a – < 2932095c114b98cbb40ccf34fc00d613cb17cead
  • Linux · Linux

    • affected 6.4
    • unaffected < 6.4
    • unaffected 6.6.134 – ≤ 6.6.*
    • unaffected 6.12.81 – ≤ 6.12.*
    • unaffected 6.18.22 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .