{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99179 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99179 is a vulnerability in Linux, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99179 and fix it if it is affected.\n\nWhat it is: CVE-2026-99179 is a vulnerability in Linux, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99179 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-99179/ (Markdown: https://insights.sbomify.com/CVE-2026-99179/index.md)","id":"CVE-2026-99179","markdown":"https://insights.sbomify.com/CVE-2026-99179/index.md","name":"CVE-2026-99179","record":{"aliases":["AZL-111338","BELL-CVE-2026-99179","DEBIAN-CVE-2026-99179","GHSA-6fpx-qf4r-r7v5","UBUNTU-CVE-2026-99179"],"analysis":null,"analysis_generated_by":null,"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\nwatch_queue: Fix note pool publication race in watch_queue_set_size()\n\nThere is a race between watch_queue_set_size() and post_one_notification().\nwatch_queue_set_size() publishes wqueue-\u003enotes, notes_bitmap, nr_pages and\nnr_notes with plain stores, and post_one_notification() reads them with\nplain loads under a different lock, so nothing orders the four stores\nagainst the poster's loads: depending on the build, notes can be stored\nlast (gcc 14 on x86-64 does this).  Since keyctl_watch_key() lets a watch\nattach to a queue before it is sized, post_one_notification() can already\nbe running on another CPU at that moment: it reads nr_notes \u003e 0, passes\nits bounds check, and then reads notes while it is still NULL,\ndereferencing notes[0].\n\nAn unprivileged user triggers this reliably by watching one of its own\nkeys through a notification pipe and racing ioctl(IOC_WATCH_QUEUE_SET_SIZE)\non that pipe against keyctl(KEYCTL_SETPERM) on the key from another CPU,\ntriggering:\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000000\n  RIP: 0010:post_one_notification.isra.0+0xa2/0x1e0\n  Call Trace:\n   __post_watch_notification+0x148/0x180\n   keyctl_setperm_key+0x119/0x130\n   do_syscall_64+0x108/0x4c0\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n  Kernel panic - not syncing: Fatal exception in interrupt\n\nFix this by publishing nr_notes last with smp_store_release(), and by\nreading it once with smp_load_acquire() in post_one_notification() before\nthe bitmap and the page array are touched.  A poster that observes a\nnon-zero nr_notes then also observes the pool behind it; one that observes\nzero drops the notification as before.","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":"watch_queue: Fix note pool publication race in watch_queue_set_size()","id":"CVE-2026-99179","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"unicode: free the map after a grace period","id":"CVE-2026-99180"},"packages":[],"prev":{"headline":"x86/kvm: Don't consume async #PF flags on a kernel #PF in NMI context","id":"CVE-2026-99178"},"products":["Linux"],"published":"2026-10-28","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-28","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-99179/"}