{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72396 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72396 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-72396 and fix it if it is affected.\n\nWhat it is: CVE-2026-72396 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-72396 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-72396/ (Markdown: https://insights.sbomify.com/CVE-2026-72396/index.md)","id":"CVE-2026-72396","markdown":"https://insights.sbomify.com/CVE-2026-72396/index.md","name":"CVE-2026-72396","record":{"aliases":["BELL-CVE-2026-72396","DEBIAN-CVE-2026-72396","GHSA-xgwj-fj27-7g4m","UBUNTU-CVE-2026-72396"],"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 with hardware access can read uninitialized kernel stack memory via the adm1275 hardware monitoring driver due to missing null termination.","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\nhwmon: adm1275: Prevent reading uninitialized stack\n\nWhile adding support for the ROHM BD127X0 hot-swap controllers, sashiko\nreported an error in device-name comparison, which can lead to reading\nuninitialized stack memory.\n\nQuoting Sashiko:\n\nThis is a pre-existing issue, but I noticed that just before this block in\nadm1275_probe(), there might be an out-of-bounds stack read:\n\n    ret = i2c_smbus_read_block_data(client, PMBUS_MFR_MODEL, block_buffer);\n    if (ret \u003c 0) { ... }\n    for (mid = adm1275_id; mid-\u003ename[0]; mid++) {\n            if (!strncasecmp(mid-\u003ename, block_buffer, strlen(mid-\u003ename)))\n                    break;\n    }\n\nSince i2c_smbus_read_block_data() reads up to 32 bytes into the\nuninitialized stack array block_buffer without appending a null\nterminator, strncasecmp() could read past the valid bytes returned in ret.\n\nFor example, if the device returns a shorter string like \"adm12\", checking\nit against \"adm1275\" up to the length of \"adm1275\" will continue reading\ninto uninitialized stack bounds.\n\nPrevent reading uninitialized memory by zeroing the stack array.","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":"hwmon: adm1275: Prevent reading uninitialized stack","id":"CVE-2026-72396","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":"hwmon: (pmbus/core) honor vrm_version in pmbus_data2reg_vid()","id":"CVE-2026-72397"},"packages":[],"prev":{"headline":"hwmon: (pmbus) Fix passing events to regulator core","id":"CVE-2026-72395"},"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 with hardware access can read uninitialized kernel stack memory via the adm1275 hardware monitoring driver due to missing null termination.","url":"https://insights.sbomify.com/CVE-2026-72396/"}