netfilter: nfnetlink_osf: fix out-of-bounds read on option matching
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1a6a0951fc009f6d9fe8ebea2d2417d80d54097b · < 21883587593d7c8bb519a79460a0b5bc5ffbdabd| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nfnetlink_osf: fix out-of-bounds read on option matching
In nf_osf_match(), the nf_osf_hdr_ctx structure is initialized once and passed by reference to nf_osf_match_one() for each fingerprint checked. During TCP option parsing, nf_osf_match_one() advances the shared ctx->optp pointer.
If a fingerprint perfectly matches, the function returns early without restoring ctx->optp to its initial state. If the user has configured NF_OSF_LOGLEVEL_ALL, the loop continues to the next fingerprint. However, because ctx->optp was not restored, the next call to nf_osf_match_one() starts parsing from the end of the options buffer. This causes subsequent matches to read garbage data and fail immediately, making it impossible to log more than one match or logging incorrect matches.
Instead of using a shared ctx->optp pointer, pass the context as a constant pointer and use a local pointer (optp) for TCP option traversal. This makes nf_osf_match_one() strictly stateless from the caller's perspective, ensuring every fingerprint check starts at the correct option offset.
From the CVE record · Linux
The Linux kernel’s nfnetlink_osf fingerprint matcher can read beyond the TCP options buffer when NF_OSF_LOGLEVEL_ALL is configured and a fingerprint matches. The next fingerprint check starts at the wrong offset, causing incorrect or missing match logs. The input does not establish whether an attacker can trigger this remotely or whether authentication or user interaction is required.
Engineers running Linux kernels that use nfnetlink_osf should check their deployments; affected versions were not provided.