GHSA-J6GG-X4G3-Q925
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32In the Linux kernel, the following vulnerability has been resolved:
iio: accel: mma8452: handle I2C read error(s) in mma8452_read()
Currently, If i2c_smbus_read_i2c_block_data() fails but mma8452_set_runtime_pm_state() succeeds, mma8452_read() returns 0.
As a result, the caller mma8452_read_raw() assumes the read was successful and proceeds to use a buffer containing uninitialized stack memory.
Add proper checking of the I2C read return value and propagate errors to the caller.
{
"affected": [],
"aliases": [
"CVE-2026-72479"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:22:22Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\niio: accel: mma8452: handle I2C read error(s) in mma8452_read()\n\nCurrently, If i2c_smbus_read_i2c_block_data() fails but\nmma8452_set_runtime_pm_state() succeeds, mma8452_read() returns 0.\n\nAs a result, the caller mma8452_read_raw() assumes the read was\nsuccessful and proceeds to use a buffer containing uninitialized\nstack memory.\n\nAdd proper checking of the I2C read return value and propagate errors\nto the caller.",
"id": "GHSA-j6gg-x4g3-q925",
"modified": "2026-08-15T06:32:26Z",
"published": "2026-08-15T06:32:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72479"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1cddef80a180af74c33d2f26c962ce92b60fded4"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5bdff291d20c31b365d9ddfe9c426fbfb41da5bb"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b488055e81d9faaaf2f8aaff45f9944040ac4493"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b4932fc325e84a3233413daf230b043818c8a824"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/eed69f8a10b82989ad732ace0fb43a9fb4e7fe35"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f3d413e701c5e54bef736b638967724dda880365"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f3d905ea1e4996d933074481e80d96ecd74a9904"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f9ec3f3e9cf27dd06cd3725eeaa44e3ce46be893"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.