mm: memcg: fix NULL pointer in mem_cgroup_track_foreign_dirty_slowpath()
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:
mm: memcg: fix NULL pointer in mem_cgroup_track_foreign_dirty_slowpath()
As commit 18365225f044 ("hwpoison, memcg: forcibly uncharge LRU pages"), hwpoison will forcibly uncharg a LRU hwpoisoned page, the folio_memcg could be NULl, then, mem_cgroup_track_foreign_dirty_slowpath() could occurs a NULL pointer dereference, let's do not record the foreign writebacks for folio memcg is null in mem_cgroup_track_foreign_dirty() to fix it.
From the CVE record · Linux
The Linux kernel can dereference a NULL pointer in mem_cgroup_track_foreign_dirty_slowpath() after hwpoison forcibly uncharges an LRU page. This can occur if foreign writeback tracking runs when the page’s memory cgroup is NULL. The input does not specify how an attacker could trigger it or whether authentication or user interaction is required.
Engineers running the Linux kernel should check their installations; affected versions are not specified.