Skip to main content
VulnerabilityPublished

CVE-2026-99719: Linux kernel · hwmon: (lm87) Fix drvdata type confusion in vrm_show() and vrm_store()

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99719· Medium

Not known to be exploited · fixed in b3b6489a11966c2e3a50574b0f08ada55530c10d : update Linux kernel when convenient.

Data as of 20 Nov 2026, 07:34 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in b3b6489a11966c2e3a50574b0f08ada55530c10d, 25ff5f904e1cb55ac700ce88db3a5a6b735b12bc, 8f5888c37a1a8f5462fdf72fb07d55f23fee5005 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to b3b6489a11966c2e3a50574b0f08ada55530c10d, 25ff5f904e1cb55ac700ce88db3a5a6b735b12bc, 8f5888c37a1a8f5462fdf72fb07d55f23fee5005 or 5b51ff0887b9f88d042b92dd07fcdda4132f0ebc.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 00a0c905ab4b2b47372be8da6a8442dcd3681903, < b3b6489a11966c2e3a50574b0f08ada55530c10d
Fixed in
  • b3b6489a11966c2e3a50574b0f08ada55530c10d
LinuxLinuxAffected
  • ≥ 00a0c905ab4b2b47372be8da6a8442dcd3681903, < 25ff5f904e1cb55ac700ce88db3a5a6b735b12bc
Fixed in
  • 25ff5f904e1cb55ac700ce88db3a5a6b735b12bc
LinuxLinuxAffected
  • ≥ 00a0c905ab4b2b47372be8da6a8442dcd3681903, < 8f5888c37a1a8f5462fdf72fb07d55f23fee5005
Fixed in
  • 8f5888c37a1a8f5462fdf72fb07d55f23fee5005
LinuxLinuxAffected
  • ≥ 00a0c905ab4b2b47372be8da6a8442dcd3681903, < 5b51ff0887b9f88d042b92dd07fcdda4132f0ebc
Fixed in
  • 5b51ff0887b9f88d042b92dd07fcdda4132f0ebc
LinuxLinuxAffected
  • =4.10
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: hwmon: (lm87) Fix drvdata type confusion in vrm_show() and vrm_store() When an LM87 or ADM1024 device is probed with VID support enabled, reading from or writing to the vrm sysfs attribute triggers a driver data type confusion in vrm_show() and vrm_store() in drivers/hwmon/lm87.c. In lm87_probe(), the driver stores the struct lm87_data pointer on the I2C client via i2c_set_clientdata() and passes the struct i2c_client pointer as the drvdata argument to devm_hwmon_device_register_with_groups(), which attaches the attribute groups to the registered hwmon device with client as its driver_data. Unlike the other sysfs callbacks that retrieve client via dev_get_drvdata() and then obtain data via i2c_get_clientdata(), vrm_show() and vrm_store() assign dev_get_drvdata(dev) directly to struct lm87_data *. Dereferencing data->vrm therefore accesses the struct i2c_client instance at offsetof(struct lm87_data, vrm), causing vrm_show() to leak an unrelated byte from struct i2c_client to userspace and vrm_store() to corrupt a byte within struct i2c_client while failing to update the actual VRM value. Fix the problem by assigning the return value from dev_get_drvdata(dev) to struct i2c_client *client and using i2c_get_clientdata() to get the actual client data.

References

Community reviews

Loading reviews…