ocfs2: fix panic in failed foilio allocation
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:
ocfs2: fix panic in failed foilio allocation
commit 7e119cff9d0a ("ocfs2: convert w_pages to w_folios") and commit 9a5e08652dc4b ("ocfs2: use an array of folios instead of an array of pages") save -ENOMEM in the folio array upon allocation failure and call the folio array free code.
The folio array free code expects either valid folio pointers or NULL. Finding the -ENOMEM will result in a panic. Fix by NULLing the error folio entry.
From the CVE record · Linux
The Linux kernel’s ocfs2 folio cleanup code can panic after a folio allocation fails because it encounters an error value where it expects a folio pointer or NULL. The input does not establish whether an attacker can trigger the failure or specify access or user-interaction requirements.
Teams running the Linux kernel with ocfs2 should check their versions; affected versions are not specified.