batman-adv: stop caching unowned originator pointers in BAT IV
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c6c8fea29769d998d94fcec9b9f14d4b52b349d3 · < 09dc0d1a12222ffca6481916eab3cfea477b9620| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
batman-adv: stop caching unowned originator pointers in BAT IV
BAT IV keeps the last-hop neighbor address in each neigh_node, but some paths also cache an originator pointer derived from a temporary lookup. That pointer is not owned by the neigh_node and may no longer refer to a live originator entry after purge handling runs.
Stop storing the auxiliary originator pointer in the BAT IV neighbor state. When BAT IV needs the neighbor originator data, resolve it from the stored neighbor address and drop the reference again after use.
[sven: avoid bonding logic for outgoing OGM]
From the CVE record · Linux
The Linux kernel's batman-adv BAT IV code can retain an unowned originator pointer that may no longer reference a live entry after purge handling. The input does not establish what an attacker could do or whether exploitation requires network access, local access, authentication, or user interaction.
Teams running the Linux kernel should check their exposure; affected versions are not specified.