{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74362 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74362 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-74362 and fix it if it is affected.\n\nWhat it is: CVE-2026-74362 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-74362 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-74362/ (Markdown: https://insights.sbomify.com/CVE-2026-74362/index.md)","id":"CVE-2026-74362","markdown":"https://insights.sbomify.com/CVE-2026-74362/index.md","name":"CVE-2026-74362","record":{"aliases":["BELL-CVE-2026-74362","DEBIAN-CVE-2026-74362","GHSA-v9mc-99cx-c56m","UBUNTU-CVE-2026-74362"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel ext2","requires_auth":"low_privilege","summary":"A local attacker can cause data loss or corruption by exploiting ignored sync errors in the ext2 filesystem, leading to silent write failures.","user_interaction":"not_required","vuln_class":"other"},"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\next2: fix ignored return value of generic_write_sync()\n\nFix ext2_dio_write_iter() to propagate the error returned by\ngeneric_write_sync() instead of silently discarding it, which could\ncause write(2) to return success to userspace on O_SYNC/O_DSYNC files\neven when the sync failed.\n\nThe correct pattern, already used in ext2_dax_write_iter() in the same\nfile and in ext4, xfs, f2fs among others, is:\n    if (ret \u003e 0)\n        ret = generic_write_sync(iocb, ret);\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.\n\n[JK: Reflect also filemap_write_and_wait() return value]","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":"ext2: fix ignored return value of generic_write_sync()","id":"CVE-2026-74362","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs","id":"CVE-2026-74363"},"packages":[],"prev":{"headline":"nvme: fix FDP fdpcidx bounds check","id":"CVE-2026-74361"},"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 cause data loss or corruption by exploiting ignored sync errors in the ext2 filesystem, leading to silent write failures.","url":"https://insights.sbomify.com/CVE-2026-74362/"}