LSM: general protection fault in legacy_parse_param
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ da2441fdffbf7602da702aea5bd95ca4dc3d63fc · < ecff30575b5ad0eda149aadad247b7f75411fd47| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
LSM: general protection fault in legacy_parse_param
The usual LSM hook "bail on fail" scheme doesn't work for cases where a security module may return an error code indicating that it does not recognize an input. In this particular case Smack sees a mount option that it recognizes, and returns 0. A call to a BPF hook follows, which returns -ENOPARAM, which confuses the caller because Smack has processed its data.
The SELinux hook incorrectly returns 1 on success. There was a time when this was correct, however the current expectation is that it return 0 on success. This is repaired.
From the CVE record · Linux
Linux kernel LSM mount-option parsing can hit a general protection fault when Smack accepts an option but a subsequent BPF hook returns an unrecognized-parameter error. The SELinux hook also incorrectly returns 1 on success. The input does not specify an attack path, authentication requirement, or user-interaction requirement.
Engineers running Linux kernels with the affected LSM behavior should check their deployments; affected versions are not specified.