{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-45977 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-45977 is a medium-severity vulnerability in Linux kernel, published on 27 May 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-45977 and fix it if it is affected.\n\nWhat it is: CVE-2026-45977 is a medium-severity vulnerability in Linux kernel, published on 27 May 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-45977 in the wild and no public exploit code.\n\nAffected product: Linux kernel. 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-45977/ (Markdown: https://insights.sbomify.com/CVE-2026-45977/index.md)","id":"CVE-2026-45977","markdown":"https://insights.sbomify.com/CVE-2026-45977/index.md","name":"CVE-2026-45977","record":{"aliases":["BELL-CVE-2026-45977","DEBIAN-CVE-2026-45977","GHSA-fgxx-jh4j-vgpg","UBUNTU-CVE-2026-45977"],"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 race condition in the fbnic driver allows a use-after-free or null dereference during teardown, potentially causing a kernel crash.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfbnic: close fw_log race between users and teardown\n\nFixes a theoretical race on fw_log between the teardown path and fw_log\nwrite functions.\n\nfw_log is written inside fbnic_fw_log_write() and can be reached from\nthe mailbox handler fbnic_fw_msix_intr(), but fw_log is freed before\nIRQ/MBX teardown during cleanup, resulting in a potential data race of\ndereferencing a freed/null variable.\n\nPossible Interleaving Scenario:\n  CPU0: fbnic_fw_msix_intr() // Entry\n          fbnic_fw_log_write()\n            if (fbnic_fw_log_ready())   // true\n            ... preempt ...\n  CPU1: fbnic_remove() // Entry\n          fbnic_fw_log_free()\n            vfree(log-\u003edata_start);\n            log-\u003edata_start = NULL;\n  CPU0: continues, walks log-\u003eentries or writes to log-\u003edata_start\n\nThe initialization also has an incorrect order problem, as the fw_log\nis currently allocated after MBX setup during initialization.\nFix the problems by adjusting the synchronization order to put\ninitialization in place before the mailbox is enabled, and not cleared\nuntil after the mailbox has been disabled.","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":"fbnic: close fw_log race between users and teardown","id":"CVE-2026-45977","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"staging: greybus: lights: avoid NULL deref","id":"CVE-2026-45978"},"packages":[],"prev":{"headline":"drm/amdgpu: Fix memory leak in amdgpu_ras_init()","id":"CVE-2026-45976"},"products":["Linux"],"published":"2026-05-27","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-27","vendors":["Linux"]},"summary":"A race condition in the fbnic driver allows a use-after-free or null dereference during teardown, potentially causing a kernel crash.","url":"https://insights.sbomify.com/CVE-2026-45977/"}