GSD-2022-1004276
dm era: commit metadata in postsuspend after worker stops
dm era: commit metadata in postsuspend after worker stops
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven. This ID is fixed in Linux Kernel version v5.18.8 by commit c593a5c135ba8ef3df1baf38524ef8bd3fe51639, it was introduced in version v3.15 by commit eec40579d84873dfb7021eb24c50360f073237c5. For more details please see the references link.
What each source reports
OSV No score
dm era: commit metadata in postsuspend after worker stops
dm era: commit metadata in postsuspend after worker stops
This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven. This ID is fixed in Linux Kernel version v5.18.8 by commit c593a5c135ba8ef3df1baf38524ef8bd3fe51639, it was introduced in version v3.15 by commit eec40579d84873dfb7021eb24c50360f073237c5. For more details please see the references link.
- Record
GSD-2022-1004276- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
KernelLinux |
Listed versions, plus commit ranges v3.14v3.15v3.15-rc1v3.15-rc2v3.15-rc3 Show 45 moreShow lessv3.15-rc4v3.15-rc5v3.15-rc6v3.15-rc7v3.15-rc8v3.16v3.16-rc1v3.16-rc2v3.16-rc3v3.16-rc4v3.16-rc5v3.16-rc6v3.16-rc7v3.17v3.17-rc1v3.17-rc2v3.17-rc3v3.17-rc4v3.17-rc5v3.17-rc6v3.17-rc7v3.18v3.18-rc1v3.18-rc2v3.18-rc3v3.18-rc4v3.18-rc5v3.18-rc6v3.18-rc7v3.19v3.19-rc1v3.19-rc2v3.19-rc3v3.19-rc4v3.19-rc5v3.19-rc6v3.19-rc7v4.0v4.0-rc1v4.0-rc2v4.0-rc3v4.0-rc4v4.0-rc5v4.0-rc6v4.0-rc7 |
None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GSD-2022-1004276 is a vulnerability with no CVSS score yet in Kernel, published July 31, 2022. No source lists public exploit code. No source names a fixed version.
Left out here: 338 versions. The JSON record has them.