Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Android Google Security

Android's Latest Update Doesn't Patch Major Security Flaw 'Dirty COW' (engadget.com) 23

The November Android security update is live and it fixes 15 critical vulnerabilities, but it doesn't patch a major Linux kernel exploit that can give hackers quick and complete access to devices running on Google's OS. From a report on Engadget: Researcher Phil Oester discovered the flaw (CVE-2016-5195) in October, though he believes it's existed since 2007. The exploit is known as "Dirty COW" because of its basis in copy-on-write systems (and maybe because that name is adorable). With this month's security update, Google did roll out a "supplemental" firmware fix for Dirty COW across Nexus and Pixel devices. Plus, Samsung released a patch for its devices this month, according to Threatpost. An official Android patch for the Dirty COW issue is expected to land in December.
This discussion has been archived. No new comments can be posted.

Android's Latest Update Doesn't Patch Major Security Flaw 'Dirty COW'

Comments Filter:
  • by Anonymous Coward on Wednesday November 09, 2016 @12:13PM (#53246793)

    I told her to root her phone, get the source code and fix it herself.

    Problem solved.

    • I told her to root her phone,

      In Australia when you use root as a verb it means to procreate. (yes this is a problem given how "gaining root access" is a more common discussion)

      I now cannot get that image out of my head. Thanks for ruining my day.

    • by antdude ( 79039 )

      What did she say and did she do it? :P

    • What's the point only about 1% of devices will actually get the patch
  • RedHat released backported Dirty Cow patches for the 2.6.18 kernel in EL5 last Friday.

    Why isn't Google using a RedHat kernel in Android, and applying the backported updates to /boot and /system, around OEM drivers?

    Why is the kernel "untouchable" by Google on non-Nexus devices? It didn't have to be this way. RedHat certainly makes kernel updates work with 3rd-party drivers. Oracle ksplice can even apply them without a reboot.

  • All you Dirty COWs go moo.

  • The flaw was discovered AFTER the patch was finalized. Until they invent time travel, there isn't much Google can do at that point. The next patch, which is the first one which will be finalized after the discovery of this flaw, will have the fix. That's really the best anyone can expect I'd think.

You knew the job was dangerous when you took it, Fred. -- Superchicken

Working...