{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-64479 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-64479 is a vulnerability in Linux, published on 25 Jul 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-64479 and fix it if it is affected.\n\nWhat it is: CVE-2026-64479 is a vulnerability in Linux, published on 25 Jul 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-64479 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-64479/ (Markdown: https://insights.sbomify.com/CVE-2026-64479/index.md)","id":"CVE-2026-64479","markdown":"https://insights.sbomify.com/CVE-2026-64479/index.md","name":"CVE-2026-64479","record":{"aliases":["BELL-CVE-2026-64479","DEBIAN-CVE-2026-64479","GHSA-6695-37p4-x7m5","ROOT-OS-UBUNTU-2204-CVE-2026-64479","UBUNTU-CVE-2026-64479"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel ALSA","requires_auth":"low_privilege","summary":"An unprivileged local user can leak 4 bytes of uninitialized kernel heap memory via the ALSA sequencer interface when specific UMP filtering conditions are met.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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\nALSA: seq: Fix uninitialised heap leak in snd_seq_event_dup()\n\nsnd_seq_event_dup() copies an incoming event into a pool cell and, in\nthe UMP-enabled build, clears the trailing cell-\u003eump.raw.extra word that\nthe memcpy() did not cover.  The guard deciding whether to clear it\ncompares the copied size against sizeof(cell-\u003eevent):\n\n\tmemcpy(\u0026cell-\u003eump, event, size);\n\tif (size \u003c sizeof(cell-\u003eevent))\n\t\tcell-\u003eump.raw.extra = 0;\n\nFor a legacy (non-UMP) event, size == sizeof(struct snd_seq_event) ==\nsizeof(cell-\u003eevent), so the condition is false and the extra word keeps\nstale data.  The cell pool is allocated with kvmalloc() (not zeroed) and\ncells are reused via a free list, so that word holds uninitialised heap\nor leftover event data.\n\nWhen such a cell is delivered to a UMP client (client-\u003emidi_version \u003e 0)\nthat set SNDRV_SEQ_FILTER_NO_CONVERT -- so the legacy event reaches it\nunconverted -- snd_seq_read() reads it out as the larger struct\nsnd_seq_ump_event and copies the stale word to user space, a 4-byte\nkernel heap infoleak to an unprivileged /dev/snd/seq client.\n\nCompare against sizeof(cell-\u003eump) instead, so the trailing word is zeroed\nfor every event shorter than the UMP cell.","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":"ALSA: seq: Fix uninitialised heap leak in snd_seq_event_dup()","id":"CVE-2026-64479","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"ALSA: ice1712: check snd_ctl_new1() return value","id":"CVE-2026-64480"},"packages":[],"prev":{"headline":"ALSA: usb-audio: avoid kobject path lookup in DualSense match","id":"CVE-2026-64478"},"products":["Linux"],"published":"2026-07-25","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":"An unprivileged local user can leak 4 bytes of uninitialized kernel heap memory via the ALSA sequencer interface when specific UMP filtering conditions are met.","url":"https://insights.sbomify.com/CVE-2026-64479/"}