{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90100 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90100 is a vulnerability in Linux, published on 17 Sep 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-90100 and fix it if it is affected.\n\nWhat it is: CVE-2026-90100 is a vulnerability in Linux, published on 17 Sep 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-90100 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-90100/ (Markdown: https://insights.sbomify.com/CVE-2026-90100/index.md)","id":"CVE-2026-90100","markdown":"https://insights.sbomify.com/CVE-2026-90100/index.md","name":"CVE-2026-90100","record":{"aliases":["BELL-CVE-2026-90100","DEBIAN-CVE-2026-90100","GHSA-rpp5-w8v3-w64q","UBUNTU-CVE-2026-90100"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A local attacker can trigger a divide-by-zero error in the Linux kernel NETC PTP driver, causing a system crash.","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\nptp: netc: fix period truncation and potential divide-by-zero in PEROUT\n\nThe max_period bound in net_timer_enable_perout() was computed as:\n\n  max_period = (u64)NETC_TMR_DEFAULT_FIPER + integral_period;\n\nwhich exceeds U32_MAX when integral_period \u003e 0 (e.g. 0x100000002 for\nthe default 333333333 Hz clock). A period_ns that passes this check but\nexceeds U32_MAX is then silently truncated when stored into the u32\nstruct netc_pp::period field.\n\nA truncated value of zero can reach netc_timer_set_perout_alarm(), where\nthe local u32 period variable would also be 0, causing a divide-by-zero\nin roundup_u64(delta, period) whenever the stime \u003c min_time branch is\ntaken (which always happens for a start time of {0, 0}).\n\nAdditionally, netc_timer_enable_periodic_pulse() and\nnetc_timer_enable_fiper() both compute:\n\n  fiper = pp-\u003eperiod - integral_period;\n\nA zero pp-\u003eperiod results in an unsigned wraparound to 0xFFFFFFFD,\nmis-programming the FIPER hardware register.\n\nFix all three issues by capping max_period at NETC_TMR_DEFAULT_FIPER\n(0xFFFFFFFF). This ensures that any period_ns passing the range check\nfits in a u32 without truncation, so the stored value is always valid\nand non-zero. The accepted range is reduced by integral_period ns\n(typically only a few nanoseconds), which is negligible in practice.","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":"ptp: netc: fix period truncation and potential divide-by-zero in PEROUT","id":"CVE-2026-90100","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"bnxt_en: Fix call to hardware monitoring event handler","id":"CVE-2026-90101"},"packages":[],"prev":{"headline":"net/sched: account classifier filter allocations to memcg","id":"CVE-2026-90099"},"products":["Linux"],"published":"2026-09-17","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-10-19","vendors":["Linux"]},"summary":"A local attacker can trigger a divide-by-zero error in the Linux kernel NETC PTP driver, causing a system crash.","url":"https://insights.sbomify.com/CVE-2026-90100/"}