bpf: Fix verifier assumptions about socket->sk
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix verifier assumptions about socket->sk
The verifier assumes that 'sk' field in 'struct socket' is valid and non-NULL when 'socket' pointer itself is trusted and non-NULL. That may not be the case when socket was just created and passed to LSM socket_accept hook. Fix this verifier assumption and adjust tests.
From the CVE record · Linux
The Linux kernel BPF verifier assumes that a trusted, non-NULL socket has a valid, non-NULL sk field. That assumption can fail when a newly created socket is passed to the LSM socket_accept hook. The input does not specify what an attacker can do or whether exploitation requires network access, authentication, or user interaction.
Engineers running the Linux kernel should check their deployments; affected versions were not provided.