{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72479 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72479 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-72479 and fix it if it is affected.\n\nWhat it is: CVE-2026-72479 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-72479 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-72479/ (Markdown: https://insights.sbomify.com/CVE-2026-72479/index.md)","id":"CVE-2026-72479","markdown":"https://insights.sbomify.com/CVE-2026-72479/index.md","name":"CVE-2026-72479","record":{"aliases":["BELL-CVE-2026-72479","DEBIAN-CVE-2026-72479","GHSA-j6gg-x4g3-q925","UBUNTU-CVE-2026-72479"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A local attacker can read uninitialized stack memory via the MMA8452 accelerometer driver due to unhandled I2C read errors.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"iio: accel: mma8452: handle I2C read error(s) in mma8452_read()","id":"CVE-2026-72479","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"iio: adc: xilinx-ams: fix out-of-bounds channel lookup in event handling","id":"CVE-2026-72480"},"packages":[],"prev":{"headline":"fs/ntfs3: add bounds check to run_get_highest_vcn()","id":"CVE-2026-72478"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A local attacker can read uninitialized stack memory via the MMA8452 accelerometer driver due to unhandled I2C read errors.","url":"https://insights.sbomify.com/CVE-2026-72479/"}