net card set VF and altname display blurred character
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kunpeng920 |
Fix Released
|
Undecided
|
Unassigned | ||
Ubuntu-20.04-hwe |
Fix Released
|
Undecided
|
Unassigned | ||
systemd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
dann frazier | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned | ||
Hirsute |
Fix Released
|
Undecided
|
Unassigned | ||
Impish |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
When running with the HWE kernel (5.4 didn't support altnames), altnames containing garbage (uninitialized memory) may get assigned to a NIC. This is 100% reproducible on arm64. The upstream commit message suggests that this has been seen to cause segfaults.
[Test Case]
1) echo 1 > /sys/class/
2) ip a
3)
10: eno1v0: <BROADCAST,
link/ether 1e:d8:e1:e9:ae:25 brd ff:ff:ff:ff:ff:ff
altname @▒ު▒
altname enp125s0f0v0
11: enp189s0f0v0: <BROADCAST,
link/ether 76:ea:f4:65:dd:33 brd ff:ff:ff:ff:ff:ff
altname ▒b▒ު▒
altname ▒▒▒▒▒▒
[Fix]
There's a one liner upstream fix that simply initializes a variable:
https:/
[What Could Go Wrong]
The fix itself is innocuous - just initializing a variable to NULL. So the real risk here would seem to be limited to the common risks in updating a core package in the Ubuntu distribution.
CVE References
Changed in systemd (Ubuntu Impish): | |
status: | New → Fix Released |
Changed in systemd (Ubuntu Hirsute): | |
status: | New → Fix Released |
Changed in systemd (Ubuntu Groovy): | |
status: | New → Fix Released |
description: | updated |
Changed in systemd (Ubuntu Focal): | |
status: | New → In Progress |
assignee: | nobody → dann frazier (dannf) |
description: | updated |
Changed in systemd (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
Changed in kunpeng920: | |
status: | New → Fix Committed |
Changed in kunpeng920: | |
status: | Fix Committed → Fix Released |
Hi,
since this is some character/encoding mess it would be helpful to get hat value those have exactly.
I mean there might be a byte swap or odd encoding somewhere, but these values might help to track down what it is.
here an example from a non-affected system (for comparison):
$ ip a | grep altname | hexdump --canonical
00000000 20 20 20 20 61 6c 74 6e 61 6d 65 20 65 6e 70 32 | altname enp2|
00000010 73 30 66 30 0a 20 20 20 20 61 6c 74 6e 61 6d 65 |s0f0. altname|
00000020 20 65 6e 70 32 73 30 66 31 0a 20 20 20 20 61 6c | enp2s0f1. al|
00000030 74 6e 61 6d 65 20 65 6e 70 32 73 30 66 32 0a 20 |tname enp2s0f2. |
00000040 20 20 20 61 6c 74 6e 61 6d 65 20 65 6e 70 32 73 | altname enp2s|
00000050 30 66 33 0a 20 20 20 20 61 6c 74 6e 61 6d 65 20 |0f3. altname |
00000060 65 6e 70 34 73 30 66 30 0a 20 20 20 20 61 6c 74 |enp4s0f0. alt|
00000070 6e 61 6d 65 20 65 6e 70 38 73 30 6e 70 30 0a 20 |name enp8s0np0. |
00000080 20 20 20 61 6c 74 6e 61 6d 65 20 65 6e 70 34 73 | altname enp4s|
00000090 30 66 31 0a |0f1.|
00000094