Heimdall Security Logo

CVE-2022-48805

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.3%
Linux•Linux•Versions : <1668781ed24da43498799aa4f65714a7de201930, 0, <711b6bf3fb052f0a6b5b3205d50e30c0c2980382, 4.14.268, <3.9, <a0fd5492ee769029a636f1fb521716b022b1423d, <=4.9.*, 5.4.180, <ffd0393adcdcefab7e131488e10dcfde5e02d6eb, <=5.10.*, <=4.14.*, 5.15.24, <63f0cfb36c1f1964a59ce544156677601e2d8740, <=5.4.*, <57bc3d3ae8c14df3ceb4e17d26ddf9eeab304581, <=4.19.*, 4.9.303, 5.10.101, <=5.16.*, 4.19.231, <=*, <=5.15.*, 5.16.10, <758290defe93a865a2880d10c5d5abd288b64b5d, 5.17, e2ca90c276e1fc410d7cd3c1a4eee245ec902a20, <9681823f96a811268265f35307072ad80713c274, 3.9

Description

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.

Gravité et risque d'exploitation

CVE-2022-48805 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.32 %, ce qui la place devant 23.2 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <1668781ed24da43498799aa4f65714a7de201930, 0, <711b6bf3fb052f0a6b5b3205d50e30c0c2980382, 4.14.268, <3.9, <a0fd5492ee769029a636f1fb521716b022b1423d, <=4.9.*, 5.4.180, <ffd0393adcdcefab7e131488e10dcfde5e02d6eb, <=5.10.*, <=4.14.*, 5.15.24, <63f0cfb36c1f1964a59ce544156677601e2d8740, <=5.4.*, <57bc3d3ae8c14df3ceb4e17d26ddf9eeab304581, <=4.19.*, 4.9.303, 5.10.101, <=5.16.*, 4.19.231, <=*, <=5.15.*, 5.16.10, <758290defe93a865a2880d10c5d5abd288b64b5d, 5.17, e2ca90c276e1fc410d7cd3c1a4eee245ec902a20, <9681823f96a811268265f35307072ad80713c274, 3.9) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE