CVE-2026-99719

published 20 Nov 2026 · updated 21 Nov 2026

hwmon: (lm87) Fix drvdata type confusion in vrm_show() and vrm_store()

5.6MediumCVSS 5.6EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel b3b6489a11966c2e3a50574b0f08ada55530c10d, Kernel 25ff5f904e1cb55ac700ce88db3a5a6b735b12bc, Kernel 5b51ff0887b9f88d042b92dd07fcdda4132f0ebc and 4 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=00a0c905ab4b2b47372be8da6a8442dcd3681903 <b3b6489a11966c2e3a50574b0f08ada55530c10d, >=00a0c905ab4b2b47372be8da6a8442dcd3681903 <25ff5f904e1cb55ac700ce88db3a5a6b735b12bc, >=00a0c905ab4b2b47372be8da6a8442dcd3681903 <5b51ff0887b9f88d042b92dd07fcdda4132f0ebc, >=00a0c905ab4b2b47372be8da6a8442dcd3681903 <8f5888c37a1a8f5462fdf72fb07d55f23fee5005, =4.10b3b6489a11966c2e3a50574b0f08ada55530c10d, 25ff5f904e1cb55ac700ce88db3a5a6b735b12bc, 5b51ff0887b9f88d042b92dd07fcdda4132f0ebc, 8f5888c37a1a8f5462fdf72fb07d55f23fee5005
linux-kernel: Kernel>=6.13.0 <6.18.64, >=6.19.0 <7.3.5, >=4.10.0 <6.12.1186.18.64, 7.3.5, 6.12.118

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99719 severity on Zeptric[![CVE-2026-99719](https://zeptric.io/badge/cve/CVE-2026-99719.svg)](https://zeptric.io/cve/CVE-2026-99719)