New: unable to handle NULL in xfrm_input+0x173, fatal exception in interrupt

Bug 76781 Daniel Borkmann 2 participants 2 messages May 23, 2014 1 message not in the archive

Subsystems (2)

Networking Network drivers

lore

Share & tools

lore

Daniel Borkmann

author

2014-05-23 08:42 UTC #1 lore raw

In reply to a message not in the archive

-------- Original Message --------
Subject: [Bug 76781] New: unable to handle NULL in xfrm_input+0x173, fatal exception in interrupt
Date: Fri, 23 May 2014 07:07:40 +0000
From: [email protected]
To: [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=76781

            Bug ID: 76781
           Summary: unable to handle NULL in xfrm_input+0x173, fatal
                    exception in interrupt
           Product: Networking
           Version: 2.5
    Kernel Version: 3.15.0-rc6
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Steffen Klassert

2014-05-23 09:16 UTC #2 lore raw

Quoted 31 lines · Daniel Borkmann

-------- Original Message --------
Subject: [Bug 76781] New: unable to handle NULL in xfrm_input+0x173, fatal exception in interrupt
Date: Fri, 23 May 2014 07:07:40 +0000
From: [email protected]
To: [email protected]
https://bugzilla.kernel.org/show_bug.cgi?id=76781
            Bug ID: 76781
           Summary: unable to handle NULL in xfrm_input+0x173, fatal
                    exception in interrupt
           Product: Networking
           Version: 2.5
    Kernel Version: 3.15.0-rc6
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No
See also the fatal oops in:
http://cateee.net/kernel/IMG_20140522_225238.jpg
http://cateee.net/kernel/IMG_20140523_082629.jpg

Quoted 7 lines

It seems it happens "often": twice in last few hours I used the new kernels. (the first oops was with 3.15.0-rc5-00270-gfba69f0)
I had also usual debian unstable updates, and I just finished to instal aiccu (a sixxs program for dynamic ip6to4, so I'm not sure it is a recent bug or just I forced it to appear in very last HEAD.

This might be fixed by these two commits:

commit edb666f07e ("xfrm6: Properly handle unsupported protocols") commit 61622cc6f2 ("xfrm4: Properly handle unsupported protocols")