xfrm interface: several kernel panic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Disco |
Fix Released
|
Medium
|
Connor Kuehl |
Bug Description
BugLink: https:/
[Impact]
Upstream has recently received a number of bug fixes that resolve kernel panics, memory leaks, and list handling for virtual xfrm interfaces that were debuted in 4.19.
[Test Case]
3 of the 5 patches have test cases in their commit message for reproducing the fault they address.
Another patch prevents including a stale name in the log files.
And the other patch that doesn't have an explicit test case improves list
handling.
[Regression Potential]
This patchset contains a nontrivial amount of changes. However, the heavier patches contain test cases that they resolve the regressions they were created for. They've been upstream since July and I don't see any follow up Fixes commits targeting these. The blast radius is "only" the xfrm interface but this is smoke tested and if any dependents rely on it for core functionality they might exercise it and would possibly notice any issues by now as well.
Original bug description follows:
-------
There was several problems reported upstream:
1/ 56c5ee1a5823: xfrm interface: fix memory leak on creation
https:/
2/ xfrm interface: avoid corruption on changelink
http://
3/ xfrm interface: ifname may be wrong in logs
http://
4/ xfrm interface: fix list corruption for x-netns
http://
CVE References
Changed in linux (Ubuntu Disco): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Connor Kuehl (connork) |
Changed in linux (Ubuntu Disco): | |
status: | In Progress → Fix Committed |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1836261
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.