HomeDefault status
unaffected
812d47889a8e418d7bea9bec383581a34c19183e (git) before b19e90521286a03bc3793fd598f20277a8f99c85
affected
812d47889a8e418d7bea9bec383581a34c19183e (git) before 44e2afbf650f3264519643fcc9e6b4d2f6e8d547
affected
812d47889a8e418d7bea9bec383581a34c19183e (git) before d9b791d8362359d241b4e8f4b4767c681ffdb6ef
affected
812d47889a8e418d7bea9bec383581a34c19183e (git) before 644ee70267a934be27370f9aa618b29af7290544
affected
f0cde54863da281cec1ed85497b4ec58d29c1460 (git)
affected
7a9239fd04802ee6ddf82d211cff3ee7df9c473a (git)
affected
Default status
affected
4.9
affected
Any version before 4.9
unaffected
5.15.124 (semver)
unaffected
6.1.43 (semver)
unaffected
6.4.8 (semver)
unaffected
6.5 (original_commit_for_fix)
unaffected
Description
In the Linux kernel, the following vulnerability has been resolved: gpio: mvebu: fix irq domain leak Uwe Kleine-König pointed out we still have one resource leak in the mvebu driver triggered on driver detach. Let's address it with a custom devm action.
Product status
812d47889a8e418d7bea9bec383581a34c19183e (git) before b19e90521286a03bc3793fd598f20277a8f99c85
812d47889a8e418d7bea9bec383581a34c19183e (git) before 44e2afbf650f3264519643fcc9e6b4d2f6e8d547
812d47889a8e418d7bea9bec383581a34c19183e (git) before d9b791d8362359d241b4e8f4b4767c681ffdb6ef
812d47889a8e418d7bea9bec383581a34c19183e (git) before 644ee70267a934be27370f9aa618b29af7290544
f0cde54863da281cec1ed85497b4ec58d29c1460 (git)
7a9239fd04802ee6ddf82d211cff3ee7df9c473a (git)
4.9
Any version before 4.9
5.15.124 (semver)
6.1.43 (semver)
6.4.8 (semver)
6.5 (original_commit_for_fix)
References
git.kernel.org/...c/b19e90521286a03bc3793fd598f20277a8f99c85
git.kernel.org/...c/44e2afbf650f3264519643fcc9e6b4d2f6e8d547
git.kernel.org/...c/d9b791d8362359d241b4e8f4b4767c681ffdb6ef
git.kernel.org/...c/644ee70267a934be27370f9aa618b29af7290544