{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40269 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40269 is a high-severity memory corruption vulnerability in Linux, published on 6 Dec 2025. 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-2025-40269 and fix it if it is affected.\n\nWhat it is: CVE-2025-40269 is a high-severity memory corruption vulnerability in Linux, published on 6 Dec 2025. 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-2025-40269 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-2025-40269/ (Markdown: https://insights.sbomify.com/CVE-2025-40269/index.md)","id":"CVE-2025-40269","markdown":"https://insights.sbomify.com/CVE-2025-40269/index.md","name":"CVE-2025-40269","record":{"aliases":["BELL-CVE-2025-40269","DEBIAN-CVE-2025-40269","GHSA-7g56-9fh3-wcxw","ROOT-OS-DEBIAN-12-CVE-2025-40269","ROOT-OS-DEBIAN-13-CVE-2025-40269","ROOT-OS-UBUNTU-2204-CVE-2025-40269","ROOT-OS-UBUNTU-2404-CVE-2025-40269","UBUNTU-CVE-2025-40269"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel USB audio","requires_auth":"low_privilege","summary":"A buffer overflow in the Linux kernel USB audio driver allows attackers to cause denial of service or execute code via malicious USB descriptors.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: usb-audio: Fix potential overflow of PCM transfer buffer\n\nThe PCM stream data in USB-audio driver is transferred over USB URB\npacket buffers, and each packet size is determined dynamically.  The\npacket sizes are limited by some factors such as wMaxPacketSize USB\ndescriptor.  OTOH, in the current code, the actually used packet sizes\nare determined only by the rate and the PPS, which may be bigger than\nthe size limit above.  This results in a buffer overflow, as reported\nby syzbot.\n\nBasically when the limit is smaller than the calculated packet size,\nit implies that something is wrong, most likely a weird USB\ndescriptor.  So the best option would be just to return an error at\nthe parameter setup time before doing any further operations.\n\nThis patch introduces such a sanity check, and returns -EINVAL when\nthe packet size is greater than maxpacksize.  The comparison with\nep-\u003epacksize[1] alone should suffice since it's always equal or\ngreater than ep-\u003epacksize[0].","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: usb-audio: Fix potential overflow of PCM transfer buffer","id":"CVE-2025-40269","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":13,"next":{"headline":"mm, swap: fix potential UAF issue for VMA readahead","id":"CVE-2025-40270"},"packages":[],"prev":{"headline":"cifs: client: fix memory leak in smb3_fs_context_parse_param","id":"CVE-2025-40268"},"products":["Linux"],"published":"2025-12-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-05","vendors":["Linux"]},"summary":"A buffer overflow in the Linux kernel USB audio driver allows attackers to cause denial of service or execute code via malicious USB descriptors.","url":"https://insights.sbomify.com/CVE-2025-40269/"}