Skip to main content
  1. Blog
  2. Article

Canonical
26 October 2017

Security Team Weekly Summary: October 26, 2017


The Security Team weekly reports are intended to be very short summaries of the Security Team’s weekly activities.

If you would like to reach the Security Team, you can find us at the #ubuntu-hardened channel on FreeNode. Alternatively, you can mail the Ubuntu Hardened mailing list at: ubuntu-hardened@lists.ubuntu.com

During the last week, the Ubuntu Security team:

  • Triaged 382 public security vulnerability reports, retaining the 130 that applied to Ubuntu.
  • Published 2 Ubuntu Security Notices which fixed 23 security issues (CVEs) across 4 supported packages.

Ubuntu Security Notices

Previous Week’s Ubuntu Security Notices

Since there was no weekly report last week, the previous week’s Ubuntu Security Notices are posted here for reference. Published 20 Ubuntu Security Notices which fixed 53 security issues (CVEs) across 27 supported packages.

Bug Triage

Mainline Inclusion Requests

Updates to Community Supported Packages

  • Simon Quigley (tsimonq2) provided debdiffs for trusty-artful for git (LP: #1719740)

Development

What the Security Team is Reading This Week

Weekly Meeting

More Info


Related posts

Accelerating delivery of CVE fixes with a new Kernel release strategy

When it comes to fixing security vulnerabilities, speed is crucial. Canonical is officially outlining a transition from its current 4-week regular and 2-week security kernel...

Canonical joins the Open Secure AI Alliance

Canonical is now part of the Open Secure AI Alliance, announced by NVIDIA with partners across cloud computing, cybersecurity, enterprise software, open source foundations, and...

Januscape vulnerability CVE-2026-53359 mitigations available

Introduction A local privilege escalation (LPE) vulnerability affecting the Linux kernel was publicly disclosed on July 6, 2026. The vulnerability was assigned CVE ID...

DirtyClone Linux kernel local privilege escalation vulnerability fixes available

On June 25, 2026, JFrog published their research into CVE-2026-43503, referring to the vulnerability as DirtyClone. The vulnerability had previously been responsibly disclosed...