Bug 1227969 (CVE-2022-48805)

Summary: VUL-0: CVE-2022-48805: kernel: net: usb: ax88179_178a: fix out-of-bounds accesses in RX fixup
Product: [Novell Products] SUSE Security Incidents Reporter: SMASH SMASH <smash_bz>
Component: IncidentsAssignee: Security Team bot <security-team>
Status: RESOLVED FIXED QA Contact: Security Team bot <security-team>
Severity: Normal    
Priority: P3 - Medium CC: camila.matos, miroslav.franc
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
URL: https://smash.suse.de/issue/414235/
Whiteboard: CVSSv3.1:SUSE:CVE-2022-48805:6.6:(AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
Found By: Security Response Team Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description SMASH SMASH 2024-07-16 17:43:54 UTC
In the Linux kernel, the following vulnerability has been resolved:

net: usb: ax88179_178a: Fix out-of-bounds accesses in RX fixup

ax88179_rx_fixup() contains several out-of-bounds accesses that can be
triggered by a malicious (or defective) USB device, in particular:

 - The metadata array (hdr_off..hdr_off+2*pkt_cnt) can be out of bounds,
   causing OOB reads and (on big-endian systems) OOB endianness flips.
 - A packet can overlap the metadata array, causing a later OOB
   endianness flip to corrupt data used by a cloned SKB that has already
   been handed off into the network stack.
 - A packet SKB can be constructed whose tail is far beyond its end,
   causing out-of-bounds heap data to be considered part of the SKB's
   data.

I have tested that this can be used by a malicious USB device to send a
bogus ICMPv6 Echo Request and receive an ICMPv6 Echo Reply in response
that contains random kernel heap data.
It's probably also possible to get OOB writes from this on a
little-endian system somehow - maybe by triggering skb_cow() via IP
options processing -, but I haven't tested that.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48805
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2022/CVE-2022-48805.mbox
https://git.kernel.org/stable/c/711b6bf3fb052f0a6b5b3205d50e30c0c2980382
https://git.kernel.org/stable/c/63f0cfb36c1f1964a59ce544156677601e2d8740
https://git.kernel.org/stable/c/1668781ed24da43498799aa4f65714a7de201930
https://git.kernel.org/stable/c/a0fd5492ee769029a636f1fb521716b022b1423d
https://git.kernel.org/stable/c/758290defe93a865a2880d10c5d5abd288b64b5d
https://git.kernel.org/stable/c/ffd0393adcdcefab7e131488e10dcfde5e02d6eb
https://git.kernel.org/stable/c/9681823f96a811268265f35307072ad80713c274
https://git.kernel.org/stable/c/57bc3d3ae8c14df3ceb4e17d26ddf9eeab304581
https://www.cve.org/CVERecord?id=CVE-2022-48805