regcache: Do not overwrite error code when finalizing cache after error
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:
regcache: Do not overwrite error code when finalizing cache after error
During regcache initialization, if an error occurs in the cache_ops->populate callback, and if cache operations include an exit callback, the error code from populate() is overwritten with the return value from exit(). This hides the error condition from the caller of regcache_init(), and can cause NULL pointer dereferences when the regcache is later accessed.
From the CVE record · Linux
During regcache initialization, an error from the populate callback can be hidden if cache operations include an exit callback. A later regcache access can then cause a NULL pointer dereference. The input does not specify an attacker path, authentication requirements, or user interaction.
Engineers running the Linux kernel should check their version against the vendor advisory; affected versions are not specified in the input.