CVE-2023-53745

What it actually does

Failure to call kfree on the params structure when uml_parse_vector_ifspec returns NULL leaves allocated memory unfreed inside the vector configuration path of the UML vector driver.

Why it matters to the business

Repeated loading or configuration of vector interfaces on long-running systems can gradually exhaust kernel memory, leading to degraded performance or eventual denial of service on affected Ubuntu 16.04 LTS kernels.

How an attack unfolds

An attacker with the ability to trigger repeated vector interface configuration operations (for example via userspace tooling or scripts that invoke the affected UML vector code path) can cause incremental memory allocations that are never released, eventually exhausting available kernel memory.

How to fix it

Upgrade to a fixed kernel package version for each affected flavor: linux 4.4.0-193.224 or later, linux-aws 4.4.0-1117.131 or later, linux-azure 4.15.0-1100.111~16.04.1 or later, linux-gcp 4.15.0-1088.101~16.04.1 or later, linux-hwe 4.15.0-126.129~16.04.1 or later, linux-kvm 4.4.0-1082.91 or later, or linux-aws (Pro 14.04) 4.4.0-1081.85 or later.

How to confirm the fix worked

After installing the updated kernel package, verify the running kernel version matches or exceeds the listed fixed version for the installed flavor and confirm that vector interface configuration no longer leaks the params allocation under test conditions.

Typical attack path

1. Identify a system running an affected Ubuntu 16.04 kernel with the UML vector driver enabled.
2. Trigger repeated calls into vector_config that cause uml_parse_vector_ifspec to return NULL.
3. Observe gradual increase in kernel memory usage without corresponding release of the params allocation.

How to detect it

Review kernel memory usage trends and dmesg or syslog entries around vector interface configuration events on systems still running the vulnerable kernels; no specific post-exploitation artifacts are known because the issue is a leak rather than an active code path that can be directly triggered by remote attackers.

What your security team should do

• Apply the listed fixed kernel packages immediately on any remaining Ubuntu 16.04 systems that still require the UML vector driver.
• Migrate workloads off Ubuntu 16.04 LTS to a supported release to eliminate exposure to this and other unpatched kernel issues.
• Audit systems for custom scripts or services that repeatedly configure UML vector interfaces and reduce unnecessary invocations until patches are deployed.