{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97480 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97480 is a vulnerability in Linux, published on 24 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-97480 and fix it if it is affected.\n\nWhat it is: CVE-2026-97480 is a vulnerability in Linux, published on 24 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-97480 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-97480/ (Markdown: https://insights.sbomify.com/CVE-2026-97480/index.md)","id":"CVE-2026-97480","markdown":"https://insights.sbomify.com/CVE-2026-97480/index.md","name":"CVE-2026-97480","record":{"aliases":["AZL-103814","BELL-CVE-2026-97480","DEBIAN-CVE-2026-97480","GHSA-jrxp-w58r-g8c9","UBUNTU-CVE-2026-97480"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel serial driver","requires_auth":"none","summary":"A NULL pointer dereference in the Linux kernel 8250 serial driver can cause a system crash when registering ports without a parent device.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\ntty: serial: 8250: protect against NULL uart-\u003eport.dev in register\n\nserial8250_register_8250_port() conditionally copies uart-\u003eport.dev\nfrom up-\u003eport.dev only when up-\u003eport.dev is non-NULL:\n\n\tif (up-\u003eport.dev) {\n\t\tuart-\u003eport.dev = up-\u003eport.dev;\n\t\t...\n\t}\n\nSo if both the existing uart slot and up have a NULL -\u003edev,\nuart-\u003eport.dev remains NULL. The very next ACPI companion check\nthen dereferences it unconditionally:\n\n\tif (!has_acpi_companion(uart-\u003eport.dev)) {\n\nhas_acpi_companion() reads dev-\u003efwnode without a NULL guard\n(include/linux/acpi.h), so this NULL-derefs the kernel for the\nremaining no-dev case rather than just skipping the\nmctrl_gpio_init() initialisation as intended.\n\nsmatch flags the inconsistency:\n\n  drivers/tty/serial/8250/8250_core.c:767\n  serial8250_register_8250_port() error: 'uart-\u003eport.dev' could be\n  null (see line 719)\n\nGuard the call with a NULL check so register continues to work\nfor callers that legitimately have no parent device (legacy\nnon-OF/non-ACPI registrations).\n\nNo functional change for callers that pass a non-NULL -\u003edev.","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":"tty: serial: 8250: protect against NULL uart-\u003eport.dev in register","id":"CVE-2026-97480","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"serial: 8250: fix possible ISR soft lockup","id":"CVE-2026-97481"},"packages":[],"prev":{"headline":"driver core: Avoid warning when removing a device while its supplier is unbinding","id":"CVE-2026-97479"},"products":["Linux"],"published":"2026-09-24","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-21","vendors":["Linux"]},"summary":"A NULL pointer dereference in the Linux kernel 8250 serial driver can cause a system crash when registering ports without a parent device.","url":"https://insights.sbomify.com/CVE-2026-97480/"}