CVE-2022-48885

What it actually does

Memory leak in ice_gnss_tty_write() where cmd_buf is not freed when write_buf allocation fails, allowing gradual kernel memory exhaustion on affected Intel E800 series devices.

Why it matters to the business

Systems using affected Linux kernel versions on supported NIC hardware may experience progressive memory pressure leading to reduced stability or forced reboots, with higher urgency for organizations running GNSS-enabled network adapters in production.

How an attack unfolds

An attacker with local access triggers repeated allocation failures in the GNSS TTY write path to exhaust kernel memory; no remote unauthenticated exploitation path or named threat actor activity is associated with this issue given its low EPSS and absence from KEV.

How to fix it

Upgrade the Linux kernel to the commit 500ca1da9d0876244eb4d1b0ece6fa0e9968d45d or later stable releases that include the fix for ice_gnss_tty_write().

How to confirm the fix worked

Confirm the running kernel contains commit 500ca1da9d0876244eb4d1b0ece6fa0e9968d45d via git log or package version checks, and verify absence of the original allocation pattern in the ice driver source.

Typical attack path

1. Obtain local access to a system with an affected ice driver
2. Trigger ice_gnss_tty_write() under conditions where write_buf allocation fails while cmd_buf succeeds
3. Repeat to accumulate leaked cmd_buf allocations until memory pressure impacts system operation

How to detect it

Review kernel logs and memory usage metrics for repeated ice driver allocation failures; inspect crash dumps or slabinfo for cmd_buf objects originating from the GNSS TTY write function.

• ice_gnss_tty_write
• write_buf alloc failed
• cmd_buf leak pattern in ice driver

What your security team should do

• Apply the referenced kernel commit immediately on systems with ice GNSS hardware
• Monitor kernel memory usage on affected hosts until patched
• Prioritize updates on production network appliances using the ice driver