Vsock connect fails with ENODEV for large CID
Bug #1813934 reported by
bugproxy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Fix Released
|
High
|
Canonical Kernel Team | ||
linux (Ubuntu) |
Fix Released
|
High
|
Skipper Bug Screeners | ||
Bionic |
Fix Released
|
High
|
Stefan Bader | ||
Cosmic |
Fix Released
|
High
|
Unassigned |
Bug Description
- Problem Descripion:
Kernel 4.19 introduced a bug in the Vsock protocol when using a large Context ID.
E.g.
CID 0xfff000 works correctly but
CID 0xfff001 fails with ENODEV when trying to connect to the listener.
The issue now also shows up in Ubuntu 18.04 with
-> kernel 4.15.0-44-generic #47-Ubuntu
on x86_64 and s390x.
It is already fixed upstream kernel by:
https:/
CVE References
tags: | added: architecture-s39064 bugnameltc-175098 severity-high targetmilestone-inin1804 |
Changed in ubuntu: | |
assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
affects: | ubuntu → linux (Ubuntu) |
Changed in ubuntu-z-systems: | |
importance: | Undecided → High |
assignee: | nobody → Canonical Kernel Team (canonical-kernel-team) |
Changed in linux (Ubuntu Bionic): | |
assignee: | nobody → Stefan Bader (smb) |
importance: | Undecided → Medium |
status: | New → In Progress |
importance: | Medium → High |
Changed in linux (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in linux (Ubuntu Cosmic): | |
importance: | Undecided → High |
status: | New → In Progress |
Changed in ubuntu-z-systems: | |
status: | New → In Progress |
Changed in linux (Ubuntu): | |
status: | Triaged → Fix Committed |
Changed in linux (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Cosmic): | |
status: | In Progress → Fix Committed |
Changed in ubuntu-z-systems: | |
status: | In Progress → Fix Committed |
Changed in ubuntu-z-systems: | |
status: | Fix Committed → Fix Released |
tags: | added: cscc |
To post a comment you must log in.
------- Comment From <email address hidden> 2019-02-05 10:24 EDT-------
When will this kernel update delivered? within the current SRU?