{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72068 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72068 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-72068 and fix it if it is affected.\n\nWhat it is: CVE-2026-72068 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-72068 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-72068/ (Markdown: https://insights.sbomify.com/CVE-2026-72068/index.md)","id":"CVE-2026-72068","markdown":"https://insights.sbomify.com/CVE-2026-72068/index.md","name":"CVE-2026-72068","record":{"aliases":["BELL-CVE-2026-72068","DEBIAN-CVE-2026-72068","GHSA-8p2j-7pmx-3hp5","UBUNTU-CVE-2026-72068"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can trigger premature CPU timer expiration on 32-bit Linux kernels via integer overflow, causing potential denial of service.","user_interaction":"not_required","vuln_class":"integer_overflow"},"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\nposix-cpu-timers: Use u64 multiplication in update_rlimit_cpu()\n\nupdate_rlimit_cpu() converts the RLIMIT_CPU value to nanoseconds with\n\n        u64 nsecs = rlim_new * NSEC_PER_SEC;\n\nOn 32-bit kernels both rlim_new (unsigned long) and NSEC_PER_SEC\n(1000000000L) are 32-bit, so the multiplication is performed in unsigned\nlong and truncated for rlim_new \u003e 4 seconds before being widened to u64.\n\nThe same file already casts to u64 for the matching computation in\ncheck_process_timers():\n\n        u64 softns = (u64)soft * NSEC_PER_SEC;\n\nAs a result, the truncated value is installed into the CPUCLOCK_PROF\nexpiry cache (nextevt), causing the process CPU timer to be programmed\nto fire prematurely for any RLIMIT_CPU soft limit \u003e= 5 seconds. The\nactual SIGXCPU/SIGKILL decision in check_process_timers() already casts\nto u64 and is therefore correct, so limit enforcement is not broken;\nonly the expiry-cache programming is wrong. Apply the same cast here so\nboth paths convert rlim_cur identically.\n\n64-bit kernels are unaffected.","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":"posix-cpu-timers: Use u64 multiplication in update_rlimit_cpu()","id":"CVE-2026-72068","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"locking/rt: Fix the incorrect RCU protection in rt_spin_unlock()","id":"CVE-2026-72069"},"packages":[],"prev":{"headline":"cpu: hotplug: Preserve per instance callback errors","id":"CVE-2026-72067"},"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 trigger premature CPU timer expiration on 32-bit Linux kernels via integer overflow, causing potential denial of service.","url":"https://insights.sbomify.com/CVE-2026-72068/"}