CVE-2026-31740

counter: rz-mtu3-cnt: do not use struct rz_mtu3_channel's dev member

State
Published
Severity
Not scored
Published
May 1, 2026
Updated
May 11, 2026
Reserved
Mar 9, 2026

Read the record on cve.org

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 0be8907359df4c62319f5cb2c6981ff0d9ebf35a to before 28a371be901ef44ee03726c2575d7d6795521fe0Affected
  • 0be8907359df4c62319f5cb2c6981ff0d9ebf35a to before 633dfbf0eb2766c597c1a59dd83035c82e14791dAffected
  • 0be8907359df4c62319f5cb2c6981ff0d9ebf35a to before 6562290225c197e2e193a53de2a517815288dcd1Affected
  • 0be8907359df4c62319f5cb2c6981ff0d9ebf35a to before 63be324c795262f0e316c6fe9b329d83afa1ec93Affected
  • 0be8907359df4c62319f5cb2c6981ff0d9ebf35a to before 2932095c114b98cbb40ccf34fc00d613cb17ceadAffected
LinuxLinux
  • 6.4Affected
  • before 6.4Not affected
  • 6.6.134 through 6.6.*Not affected
  • 6.12.81 through 6.12.*Not affected
  • 6.18.22 through 6.18.*Not affected
  • 6.19.12 through 6.19.*Not affected
  • 7.0 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.