{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80970 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80970 is a vulnerability in Linux, published on 11 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-80970 and fix it if it is affected.\n\nWhat it is: CVE-2026-80970 is a vulnerability in Linux, published on 11 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-80970 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-80970/ (Markdown: https://insights.sbomify.com/CVE-2026-80970/index.md)","id":"CVE-2026-80970","markdown":"https://insights.sbomify.com/CVE-2026-80970/index.md","name":"CVE-2026-80970","record":{"aliases":["BELL-CVE-2026-80970","DEBIAN-CVE-2026-80970","GHSA-x4cq-72c3-qv9j","UBUNTU-CVE-2026-80970"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can read uninitialized kernel memory via the ALSA FCP driver, potentially exposing sensitive kernel data.","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: FCP: do not copy out an uninitialised init response\n\nfcp_ioctl_init() allocates its response buffer with kmalloc() and copies\nthe whole buffer back to userspace:\n\n\tbuf_size = init.step0_resp_size + init.step2_resp_size;\n\n\tvoid *resp __free(kfree) =\n\t\tkmalloc(buf_size, GFP_KERNEL);\n\t...\n\tif (copy_to_user(arg-\u003eresp, resp, buf_size))\n\t\treturn -EFAULT;\n\nNothing clears the buffer, and the only writer of its leading\nstep0_resp_size bytes is the step-0 control transfer:\n\n\terr = snd_usb_ctl_msg(dev, usb_rcvctrlpipe(dev, 0),\n\t\tFCP_USB_REQ_STEP0,\n\t\tUSB_RECIP_INTERFACE | USB_TYPE_CLASS | USB_DIR_IN,\n\t\t0, private-\u003ebInterfaceNumber,\n\t\tstep0_resp, private-\u003estep0_resp_size);\n\tif (err \u003c 0)\n\t\treturn err;\n\nusb_fill_control_urb() does not set URB_SHORT_NOT_OK, so a short or\nzero-length data stage completes with status 0 and snd_usb_ctl_msg()\nreturns a small actual_length.  The only check is err \u003c 0, so a short\ntransfer is accepted as success.\n\nsnd_usb_ctl_msg() copies the full size back unconditionally:\n\n\tbuf = kmemdup(data, size, GFP_KERNEL);\n\t...\n\tmemcpy(data, buf, size);\n\nBytes the device never wrote are therefore restored into resp unchanged\nand copied to userspace.  step0_resp_size and step2_resp_size are each\nvalidated only to 1..255, so the caller also picks the slab cache, from\nkmalloc-8 up to kmalloc-512.\n\nOn 7.2.0-rc5 (arm64), device answering step 0 with a zero-length data\nstage, s0 = s2 = 255:\n\n  # init_on_alloc off, no spray\n  step0 window [0,255): nonzero=94/255\n  000: 00 80 60 06 00 00 ff ff 18 00 00 00 57 01 ea 01\n  010: 08 78 22 13 00 00 ff ff a8 c4 5f 80 00 80 ff ff\n\n  # same kernel, kmalloc-512 pre-seeded with an 8-byte tag\n  step0 window [0,255): nonzero=219/255  tagbytes=232\n\n  # identical run, init_on_alloc=1\n  step0 window [0,255): nonzero=0/255  tagbytes=0\n\n  # all three runs\n  step2 window [255,510): device words matched=62/62\n\na8 c4 5f 80 00 80 ff ff is the little-endian kernel text address\nffff8000805fc4a8.  The step-2 window is unaffected, so the disclosure is\nexactly the step-0 region.\n\nZero the buffer, and require the step-0 transfer to deliver the full\nstep0_resp_size bytes so a short data stage is reported as an error.\n\nDiscovered by XBOW, triaged by Baul Lee \u003cbaul.lee@xbow.com\u003e","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: FCP: do not copy out an uninitialised init response","id":"CVE-2026-80970","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"ALSA: bcd2000: clear the URB pointers on disconnect","id":"CVE-2026-80971"},"packages":[],"prev":{"headline":"ALSA: mpu401: Check card index validity at probe","id":"CVE-2026-80969"},"products":["Linux"],"published":"2026-09-11","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 read uninitialized kernel memory via the ALSA FCP driver, potentially exposing sensitive kernel data.","url":"https://insights.sbomify.com/CVE-2026-80970/"}