It was discovered that libnl incorrectly handled memory when performing
certain operations. A local attacker could possibly use this issue to cause
libnl to crash, resulting in a denial of service, or execute arbitrary
code.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
Ubuntu | 17.04 | noarch | libnl-3-200 | <Â 3.2.29-0ubuntu2.1 | UNKNOWN |
Ubuntu | 17.04 | noarch | libnl-3-200-dbg | <Â 3.2.29-0ubuntu2.1 | UNKNOWN |
Ubuntu | 17.04 | noarch | libnl-3-200-dbgsym | <Â 3.2.29-0ubuntu2.1 | UNKNOWN |
Ubuntu | 17.04 | noarch | libnl-3-200-udeb | <Â 3.2.29-0ubuntu2.1 | UNKNOWN |
Ubuntu | 17.04 | noarch | libnl-3-200-udeb-dbgsym | <Â 3.2.29-0ubuntu2.1 | UNKNOWN |
Ubuntu | 17.04 | noarch | libnl-3-dev | <Â 3.2.29-0ubuntu2.1 | UNKNOWN |
Ubuntu | 17.04 | noarch | libnl-3-dev-dbgsym | <Â 3.2.29-0ubuntu2.1 | UNKNOWN |
Ubuntu | 17.04 | noarch | libnl-cli-3-200 | <Â 3.2.29-0ubuntu2.1 | UNKNOWN |
Ubuntu | 17.04 | noarch | libnl-cli-3-200-dbgsym | <Â 3.2.29-0ubuntu2.1 | UNKNOWN |
Ubuntu | 17.04 | noarch | libnl-cli-3-dev | <Â 3.2.29-0ubuntu2.1 | UNKNOWN |